User talk:65.113.30.141

Sailfish OS

Developer	Jolla
Written in	Qt/QML, C++
OS family	Linux
Working state	Current
Source model	Open source with added closed-source components and extensions of third parties which can be of other licences as well.
Latest release	4.1.0.24 (Kvarken) / 27 May 2021 (2021-05-27)
Latest preview	4.1.0.24 (Kvarken) / 24 May 2021 (2021-05-24)
Marketing target	Mobile and general purpose
Available in	English for development, SDK & supporting documentation; over 21 national languages versions of UI in user's device
Package manager	RPM Package Manager
Platforms	32-bit ARM and 64-bit x86
Kernel type	Linux kernel
Userland	GNU
License	For end-user the EULA defines used open source and other licences components with a component's origin.
Preceded by	MeeGo by alliance of Nokia & Intel
Official website	sailfishos.org

Hackday with Jolla, Mer and Nemo Mobile in September 2012

Sailfish OS is a Linux-based operating system based on free software, and open source projects such as Mer as well as including a closed source UI. The project is being developed by the Finnish company Jolla.

The OS is shipped with the Jolla smartphone and tablet (the sale stopped in 2016 but devices are still supported with software updates) and from other vendors licensing the OS. The OS is ported by community enthusiasts to third-party mobile devices including smartphones and tablet computers. Sailfish OS can be used for many kinds of devices.

History and development

The OS is an evolved continuation of the Linux MeeGo OS previously developed by alliance of Nokia and Intel which itself relies on combined Maemo and Moblin. The MeeGo legacy is contained in the Mer core in about 80% of its code; the Mer name thus expands to MEego Reconstructed. This base is extended by Jolla with a custom user interface and default applications. Jolla and MERproject.org follow a meritocratic system to avoid the mistakes that led to the MeeGo project's then-unanticipated discontinuation.

The main elements for Sailfish OS 2.0 include:

• Technically stronger OS core
• Improved Android application compatibility
• Support for ARM and Intel architectures, including the Intel Atom x3 processor, or any platform with kernel useable (settle-able) for MER core stack (also called middleware of Sailfish).
• Design to provide visibility in the UI for digital content providers and to enable OS level integration for mobile commerce
• Strong multitasking (one of the most important advantage of the OS and declared to be the best one on the market)
• Strong privacy and personalization features
• Enhanced user interface with new UI/UX features, including simpler swipe access to main functions, enhanced notifications and events views.

Software architecture

The Sailfish OS and the Sailfish software development kit (SDK) are based on the Linux kernel and Mer. Sailfish OS includes a multi-tasking graphical shell called "Lipstick" built by Jolla on top of the Wayland display server protocol. Jolla uses free and open-source graphics device drivers but the Hybris library allows use of proprietary drivers for Android. Jolla's stated goal is for Sailfish to be open source eventually.

Sailfish OS can run Android applications through a proprietary compatibility layer.

Targeted device classes

Sailfish is commonly known to be targeted at mobile devices, but since it inherited around 80% of MeeGo code, Sailfish can be used as a complete general-purpose Linux OS on devices including in vehicle infotainment (IVI), navigation, smart TV, desktops and notebooks, yachts, automotive, e-commerce, home appliances, measuring and control equipment, smart building equipment, etc. See use cases of original MeeGo to compare, and the Devices section for devices that run the Sailfish OS.

Sailfish OS SDK

The Sailfish OS SDK was announced at the Slush Helsinki conference in 2012, and the alpha was published in February 2013. The SDK, installation and coding tutorials are available for free download from the Sailfish OS website despite the overall license not being open source.

Sailfish SDK uses Qt with VirtualBox for development, compiling and emulation purposes, in contrast to the simulation method. This technique allows compilation on the Sailfish OS and full testing of developed software in the virtual machine, emulating – not simulating – the whole Sailfish OS. This also separates development activities and side effects from everything else running on the host computer, leaving it undisturbed by developments and tests. According to Jolla, development with Sailfish SDK is development on Sailfish OS itself; there are no differences between developed software appearance and behaviour in the SDK and on a device running Sailfish OS.

The availability of source code to the SDK allows shaping and rebuilding to companies' or developers' specific needs, creating a context-specific environment that is set once and needs no preparation when the device is booted. The SDK runs on the operating systems Android, 32- and 64-bit versions of Linux, 64-bit versions of OS X, and Microsoft Windows. It can be used for compiling software for Sailfish OS devices from Linux sources. Its general console/terminal mode follows a commonly used standard. Compatible binaries or libraries can also be used.

Application programming interfaces

Sailfish OS uses open source Qt APIs (Qt 5, QtQuick 2 etc.) and a closed source Sailfish Silica for the UI. Standard Linux APIs are provided by the Mer Core.

Sailfish, Ubuntu and Plasma Active have been cooperating to share common APIs. When successful, this will make the platforms compatible on the API level.

Software overview

Sailfish OS version 2.0.2.51 running on Intex Technologies Aqua Fish

UI supported human languages

Officially Jolla declares supporting the following 14 languages for the user interface: Danish, German, English (UK), Spanish, French, Italian, Norwegian, Polish, Portuguese, Finnish, Swedish, Russian, Chinese (Mainland), and Chinese (Hong Kong). For each of them, the OS has a dedicated keyboard. There are a few more languages which are unofficially supported by community freelancers not under control by Jolla, hence more than 20 languages are supported in total. Additional languages can be installed by skilled users due to the Linux architecture.

Public "Early access" for beta testers and developers

After positive experiences with pushing early updates to a small group of opt-in users for Sailfish Update 9 and for the connectivity hotfix, Jolla has allowed all interested parties to try a new version of Sailfish OS about 1–2 weeks before official release, in a program called "Early access". It is expected to be useful for developers and technically minded users, and a step towards more community integration into the Sailfish release process, including improvement of quality by identifying critical issues which only show up in certain environments or device setups, before rolling the update out to the wider user audience. As an added bonus, it provides a window for developers to test their applications on new releases of Sailfish OS.

In the long term it will help Jolla to establish a developer program with early release candidate access for registered developers, and to have more community involvement in platform development. The first detail Jolla is hoping to learn from this is how it can gather feedback from a large audience in a reasonable way.

Basic details about the early access update:

• The early release access is meant primarily for advanced users and developers.
• To sign up for the program there is a checkbox in the Jolla accounts profile page.
• Installed early-access release cannot be downgraded. The only way to downgrade from early access releases is to do a factory reset after removing the sign up check from the user's account profile.
• Early access releases should be considered "reasonably stable". Issues found during that period will either be fixed, or added to "known issues" on the release notes.
• Signing up for the early access releases will not void warranty.

Version history

Sailfish OS has three naming conventions: version number, update number and version name.

• Sailfish 1.0 versions were named after Finnish lakes.
• Sailfish 2.0 supports the Jolla Tablet with x86 platforms and featured a reworked touch based UI. Releases were named after Finnish rivers.
• Sailfish 3.0 and 4.0 features a slightly reworked UI. Releases are named after Finnish national parks.

Stop releases

When updating SFOS from earlier releases, for example after device factory reset, there are several stop releases which cannot be skipped and must be taken before continuing on the path to following releases. These releases provide new functionality that is not compatible with previous releases and have to be traversed in order not to lose data or put the OS into an unstable state.

Software version	Release date	Name
v1.0.2.5	27 December 2013	Maadajävri
v1.1.2.16	25 February 2015	Yliaavanlampi
v1.1.7.28	31 August 2015	Björnträsket
v1.1.9.30	22 October 2015	Eineheminlampi
v2.0.0.10	3 November 2015	Saimaa
v2.2.0.29	7 June 2018	Mouhijoki
v3.0.0.8	11 November 2018	Lemmenjoki
v3.2.0.12	5 November 2019	Torronsuo
v3.4.0.24	13 October 2020	Pallas-Yllästunturi
v4.0.1.48	16 February 2021	Koli

Porting

The Sailfish website publishes an online compendium of knowledge, links and instructions on porting issues.

Using Android software running on Sailfish OS

In addition to its native applications, Sailfish can run most Android applications by installing them from an application store or directly through an APK file. Supported Android versions are 4.1.2 "Jelly Bean" on the original Jolla phone; 4.4.4 "Kit-Kat" on the Jolla C, Jolla tablet and Xperia X; 8.1.0 "Oreo" on Xperia XA2 and Xperia 10. Problems can arise if these applications were built without following Android standards about controls, which might not display correctly and so become unusable.

Sailfish OS uses Alien Dalvik, a proprietary Android compatibility layer. It does not emulate a copy of Android, but instead implements its APIs, an approach comparable to that of Wine. Android applications can thus run at native speed without any perceivable slow-down. Sailfish can run both native Sailfish and Android software simultaneously, with the user switching between them on the fly.

Devices having Android 8.1 support are using LXC to improve the security with better isolation, in the same way the open source Android compatibility layer Anbox is doing.

Hardware overview

Advantages of the Mer standard

Sailfish OS can be used on any hardware with Linux-kernel support and compatible with the middleware utilising the Mer core. Community enthusiasts have ported Sailfish OS to a number of devices this way. Instead of designation to a specific reference hardware platform, a VirtualBox implementation with the Sailfish OS SDK is available for development on Linux, OS X and Windows operating systems. This virtual machine implementation contains the whole Sailfish OS isolated from local resources and the local OS to enable convenient evaluation of the behaviour and performance of coded or ported software before deployment on real devices.

Jolla devices

• Jolla C
• Jolla Tablet
• Jolla Phone

Devices from other vendors licensing Sailfish OS

Manufacturers can provide mobile equipment with a licensed Sailfish OS, or as open source, or combining both and including their own or the operator's modifications and branding for specific markets or purposes.

• Qtech QMP-M1-N – Aurora
• Aquarius Cmp NS220 – Aurora
• MIG C55 – Aurora
• Aquarius Cmp NS208 – Aurora
• Sony Xperia 10 Plus – via Sailfish X
• Sony Xperia 10 – via Sailfish X
• Blackview BV6000s – Sailfish OS Rus
• Inoi T8 – Sailfish OS Rus
• Planet Computers Gemini PDA – via Sailfish X
• Sony Xperia XA2 Plus – via Sailfish X
• Sony Xperia XA2 Ultra – via Sailfish X
• Sony Xperia XA2 – via Sailfish X
• Sony Xperia X – via Sailfish X
• Inoi R7 – Sailfish OS Rus
• TRI Turing Phone
• Intex Aqua Fish

Planned and announced devices

Several devices have been announced with official support for Sailfish OS for future release.

• Qtech QMP-M1-N IP68 – listed for porting to Aurora by OMP on their website in late 2019 or early 2020
• MIG T8 – listed for porting to Aurora by OMP on their website in late 2019 or early 2020
• Inoi 5i pro – listed for porting to Aurora by OMP on their website in late 2019 or early 2020
• Вектор – listed for porting to Aurora by OMP on their website in late 2019 or early 2020
• F(x)tec Pro1 – announced with Sailfish OS support; released 2019; no official Sailfish OS support yet
• Planet Computers Cosmo Communicator – crowdfunded in December 2018; released in 2019
• INOI T10 – announced in 2018 for B2B, not available in retail
• Inoi R7 Rugged – publicly shown by Jolla, but never seen available

Cancelled devices:

• Youyota Tablet – crowdfunding in 2017; cancelled in 2018
• PuzzlePhone – announced in 2015 with Sailfish OS support; delayed indefinitely in 2017
• Oysters SF – announced for 2016; not released
• Ermak 50 – announced for Q3/2016; not released
• mi-Fone – announced in 2016 for Q2/2016; not released
• Jala Accione and Jala Accione P – Announced in 2017; a beta test of Sailfish OS was announced on Feb. 22, 2019, but sales with Sailfish OS preinstalled were cancelled and sold with only Android.

Community enthusiasts' ports to devices from other vendors

Due to the relative ease of porting and the open source license, Sailfish OS has also been unofficially ported to other 3rd-party devices. The Hardware Adaptation Development Kit for porters has been published and is free. These ports are mostly published on the Maemo and XDA Developers forums, and in the Mer wiki a list of the ports is compiled. Due to license restrictions, proprietary parts or extensions such as the Alien Dalvik compatibility layer for Android apps are not included. However they can be added, e.g. when a manufacturer or distributor turns it from the community version into an officially supported version for a particular device. From the originally more than 80 ports, there are about 19 ports that are still in active development – as of March 2019 – meaning they have been updated to Sailfish 3:

• Alcatel Idol 3
• Fairphone 2
• F(x)tec Pro1
• HP TouchPad
• Motorola Moto Z Play
• Motorola Photon Q
• Motorola Moto X Force
• Motorola Moto X 2014
• Motorola Moto G 2014
• Motorola Moto G 2015
• Motorola Moto G4 Plus
• OnePlus X
• OnePlus One
• OnePlus 3
• OnePlus 3T
• OnePlus 5
• OnePlus 5T
• Samsung Galaxy A5
• Sony Xperia X Compact
• Xiaomi Redmi 2
• Xiaomi Redmi Note 3
• Xiaomi Redmi Note 4
• Xiaomi Redmi 5 Plus
• Xiaomi Redmi 4X

To display the ease of porting Sailfish OS to other devices, Jolla showed created ports and community ports at events like the Mobile World Congress, Slush and FOSDEM:

• Nokia N950
• Nokia N9
• Google Nexus 7
• Google Nexus 4
• Samsung Galaxy S3
• Xiaomi Mi 2
• TCL Idol X950
• Google Nexus 5
• Fairphone 2
• Sony Xperia X
• Jolla Sailfish Watch
• Sony Xperia XA2
• Planet Computers Gemini PDA
• a feature phone similar to the Nokia 3310 assumed to be the chinese Kingsun EF33

Jolla's Russian partner Open Mobile Platform (OMP) showed Aurora OS ported to different devices on their YouTube channel:

• Aquarius Cmp NS220
• Qtech QMP-M1-N
• MIG C55
• Салют ЗЛ24ПМ
• Blackview BV6000s
• Aquarius Cmp NS208

OS development status

Sailfish OS is promoted by Jolla and supported by the open Sailfish Alliance established in 2011, a group established to unite OEM and ODM manufacturers, chipset providers, operators, application developers and retailers. On 16 August 2012, the user interface was reported to be ready for release. Jolla's CEO Jussi Hurmola stated in a ZDNet interview, " ... Our UI is ready now, we haven't released it yet, we will save it for the product launch and the platform is getting up now so the project looks pretty nice".

The next day, Jolla's CEO Marc Dillon said on social networking website Twitter that the company had reached the first development target. Sailfish was debuted by the Jolla team, including a worldwide internet stream, as a demo of the OS, and the UI and SDK during the Slush event in Helsinki, Finland, on 21–22 November 2012. The alpha stage of Sailfish OS SDK was published at the end of February 2013 and was made available for free download.

On 16 September 2013, Jolla announced that its OS had been made compatible with Android applications and hardware. The first telephone to use it was launched on 27 November 2013 at a pop-up DNA Kauppa shop in Helsinki. The first 450 telephones were sold at this event, while the rest of the preordered devices were shipped shortly after.

In September 2015, version 1.1.9.28 "Eineheminlampi" was released, which added the main elements of the revamped Sailfish OS 2.0 user interface.

Sailfish 2.0 was launched with the Jolla Tablet, and existing devices, both smartphones and tablets, from Jolla's official distribution channels are supported with upgrade to Sailfish 2.0 and following updates.

In May 2016 Jolla announced the Sailfish Community Device Program, supporting developers and members of Sailfish OS community.

Aurora OS

Jolla staff met with members of the Russian technology community to break ground on the new software and promote Sailfish OS, as part of Jolla's BRICS strategy. As a result of those efforts, on 18 May 2015 the Russian minister of communications Nikolai Nikiforov announced plans to replace Apple's iOS and Google's Android platforms with new software based on Sailfish. He intends it to cover 50% of Russian needs in this area during next ten years, in comparison to the 95% currently covered with western technology. The Russian version is currently being developed under the brand name Aurora (Avrora) OS. The Chinese multinational technology company Huawei may start using Aurora OS as Android's replacement.

Sailfish Alliance

Sailfish Alliance is the open alliance established in 2011 by Jolla company to support the MeeGo ecosystem with new products, services and business opportunities around or using Sailfish OS, a Linux operating system combining mer with proprietary components from Jolla and other parties, for various purposes and mobile devices. And to continue the development of the Linux MeeGo ecosystem, which the Sailfish OS is a part of.

The alliance is seen as a competitor to other groups like Android's Open Handset Alliance.

In 2011 some of the MeeGo team working at Nokia left, and were funded by Nokia though their "Bridge" program to fund spin-out projects by ex-employees. The Sailfish Alliance has sought to collaborate between the Finnish software developers, and overseas handset manufacturers, some of which are in China. The news media reports that a number of manufacturers in China and India want an alternative to Android.

The Alliance aims to "unite OEM and ODM manufacturers, chipset providers, operators, application developers and retailers."

Business strategy

The aim of the Alliance is to offer unique differentiation opportunities and sustainable competitive advantage for OEM and ODM manufacturers, chipset providers, operators, application developers, retailers and other interested in sides.

Sailfish Secure

The Sailfish Secure is the first open and secure mobile phone platform, the secure mobile solution based on Sailfish OS. For the first time it was introduced publicly in Barcelona, Spain at Mobile World Congress on 2 March 2015 where plans for the Sailfish Secure were presented.

Established on foundations of a security-hardened version of the Sailfish OS and SSH's communication encryption and key management platform. Developed by Jolla (the Sailfish OS designer and developer) together with SSH Communications Security (the inventor of Secure Shell SSH protocol, among other advanced security projects it provides) in collaboration of Sailfish Alliance.

The hardware platform independent approach of the Sailfish Secure allow concept adaptation to e.g. local needs, and also in collaboration with other security partners. End customers like governments or large corporations are able to adapt the solution to their preferred or used hardware platform, as it is not tied to a specific hardware or configuration.

The aim is to answer increasing demand in privacy in mobile communications. Jolla and Sailfish OS has unique position to create and provide an alternative solution on markets dominated by Android or other non-EU based OSes. Target customers need a secure mobile solution, including government officials or corporations, but it is also to be the solution affordable for consumers.

See also

• Comparison of mobile operating systems
• Sailfish smartwatch
• Nokia Asha platform
• Nokia X platform
• KaiOS
• Hongmeng OS

External links

• SailfishOSwiki, a site hosting Sailfish OS documentation
• Building Sailfish OS packages manually (including porting over existing applications that use a different build system)
• Jolla website
• OpenRepos.net
• Why Sailfish is better as a modern OS? Here is a comparison
• FlyingSheep on Sailfish – a good reading for developers and porting from MeeGo Harmattan to Sailfish OS

RPM Package Manager (RPM)

Original author(s)	Erik Troan, Marc Ewing, Red Hat
Developer(s)	Community & Red Hat
Initial release	1997 (1997)
Stable release	4.16.1.3 / 22 March 2021 (2021-03-22)
Preview release	4.17.0 alpha / 26 April 2021 (2021-04-26)
Written in	C, Perl
Operating system	Linux, Unix-like
Type	Package management system
License	GPL
Website	rpm.org

RPM Package Manager (RPM) (originally Red Hat Package Manager, now a recursive acronym) is a free and open-source package management system. The name RPM refers to .rpm file format and the package manager program itself. RPM was intended primarily for Linux distributions; the file format is the baseline package format of the Linux Standard Base.

Although it was created for use in Red Hat Linux, RPM is now used in many Linux distributions such as Fedora, CentOS, OpenSUSE, OpenMandriva and Oracle Linux. It has also been ported to some other operating systems, such as Novell NetWare (as of version 6.5 SP3), IBM's AIX (as of version 4), IBM i, and ArcaOS.

An RPM package can contain an arbitrary set of files. Most RPM files are “binary RPMs” (or BRPMs) containing the compiled version of some software. There are also “source RPMs” (or SRPMs) containing the source code used to build a binary package. These have an appropriate tag in the file header that distinguishes them from normal (B)RPMs, causing them to be extracted to /usr/src on installation. SRPMs customarily carry the file extension “.src.rpm” (.spm on file systems limited to 3 extension characters, e.g. old DOS FAT).

History

RPM was originally written in 1997 by Erik Troan and Marc Ewing, based on pms, rpp, and pm experiences.

pm was written by Rik Faith and Doug Hoffman in May 1995 for Red Hat Software, its design and implementations influenced greatly by pms, a package management system by Faith and Kevin Martin in the fall of 1993 for the Bogus Linux Distribution. pm preserves the "Pristine Sources + patches" paradigm of pms, while adding features and eliminating arbitrary limitations present in the implementation. pm provides greatly enhanced database support for tracking and verifying installed packages

Features

For a system administrator performing software installation and maintenance, the use of package management rather than manual building has advantages such as simplicity, consistency and the ability for these processes to be automated and non-interactive. rpm uses Berkeley DB as the backend database although since 4.15 in 2019, it supports building rpm packages without Berkeley DB (–disable-bdb).

Features of RPM include:

• RPM packages can be cryptographically verified with GPG and MD5
• Original source archive(s) (e.g. .tar.gz, .tar.bz2) are included in SRPMs, making verification easier
• Delta update: PatchRPMs and DeltaRPMs, the RPM equivalent of a patch file, can incrementally update RPM-installed software
• Automatic build-time dependency evaluation.

Local operations

Packages may come from within a particular distribution (for example Red Hat Enterprise Linux) or be built for it by other parties (for example RPM Fusion for Fedora). Circular dependencies among mutually dependent RPMs (so-called "dependency hell") can be problematic; in such cases a single installation command needs to specify all the relevant packages.

Repositories

RPMs are often collected centrally in one or more repositories on the internet. A site often has its own RPM repositories which may either act as local mirrors of such internet repositories or be locally maintained collections of useful RPMs.

Front ends

Several front-ends to RPM ease the process of obtaining and installing RPMs from repositories and help in resolving their dependencies. These include:

• yum used in Fedora, CentOS 5 and above, Red Hat Enterprise Linux 5 and above, Scientific Linux, Yellow Dog Linux and Oracle Linux
• DNF, introduced in Fedora 18 (default since 22), Red Hat Enterprise Linux 8 and CentOS Linux 8.
• up2date used in Red Hat Enterprise Linux, CentOS 3 and 4, and Oracle Linux
• Zypper used in Mer (and thus Sailfish OS), MeeGo, openSUSE and SUSE Linux Enterprise
• urpmi used in Mandriva Linux, ROSA Linux and Mageia
• apt-rpm, a port of Debian's Advanced Packaging Tool (APT) used in Ark Linux, PCLinuxOS and ALT Linux
• Smart Package Manager, used in Unity Linux, available for many distributions including Fedora.
• rpmquery, a command-line utility available in (for example) Red Hat Enterprise Linux

Local RPM installation database

Working behind the scenes of the package manager is the RPM database, stored in /var/lib/rpm. It uses Berkeley DB as its back-end. It consists of a single database (Packages) containing all of the meta information of the installed RPMs. Multiple databases are created for indexing purposes, replicating data to speed up queries. The database is used to keep track of all files that are changed and created when a user (using RPM) installs a package, thus enabling the user (via RPM) to reverse the changes and remove the package later. If the database gets corrupted (which is possible if the RPM client is killed), the index databases can be recreated with the rpm --rebuilddb command.

Description

Whilst the RPM format is the same across different Linux distributions, the detailed conventions and guidelines may vary across them.

Package filename and label

An RPM is delivered in a single file, normally with a filename in the format:

<name>-<version>-<release>.src.rpm for source packages, or

<name>-<version>-<release>.<architecture>.rpm for binaries.

For example, in the package filename libgnomeuimm-2.0-2.0.0_3.i386.rpm, the <name> is libgnomeuimm, the <version> is 2.0, the <release> is 2.0.0_3, and the <architecture> is i386. The associated source package would be named libgnomeuimm-2.0-2.0.0_3.src.rpm

RPMs with the noarch.rpm extension do not depend on a particular CPU architecture. For example, these RPMs may contain graphics and text for other programs to use. They may also contain shell scripts or programs written in other interpreted programming languages such as Python.

The RPM contents also include a package label, which contains the following pieces of information:

• software name
• software version (the version taken from original upstream source of the software)
• package release (the number of times the package has been rebuilt using the same version of the software). This field is also often used for indicating the specific distribution the package is intended for by appending strings like "mdv" (formerly, "mdk") (Mandriva Linux), "mga" (Mageia), "fc4" (Fedora Core 4), "rhl9" (Red Hat Linux 9), "suse100" (SUSE Linux 10.0) etc.
• architecture for which the package was built (i386, i686, x86_64, ppc, etc.)

The package label fields do not need to match the filename.

Library packaging

Libraries are distributed in two separate packages for each version. One contains the precompiled code for use at run-time, while the second one contains the related development files such as headers, etc. Those packages have "-devel" appended to their name field. The system administrator should ensure that the versions of the binary and development packages match.

Binary format

The format is binary and consists of four sections:

• The lead, which identifies the file as an RPM file and contains some obsolete headers.
• The signature, which can be used to ensure integrity and/or authenticity.
• The header, which contains metadata including package name, version, architecture, file list, etc.
• A file archive (the payload), which usually is in cpio format, compressed with gzip. The rpm2cpio tool enables retrieval of the cpio file without needing to install the RPM package.
  • The Linux Standard Base requires the use of gzip, but Fedora 30 packages are xz-compressed and Fedora 31 packages might be zstd-compressed. Recent versions of RPM can also use bzip2, lzip, or lzma compression.
  • RPM 5.0 format supports using xar for archiving.

SPEC file

The "Recipe" for creating an RPM package is a spec file. Spec files end in the ".spec" suffix and contain the package name, version, RPM revision number, steps to build, install, and clean a package, and a changelog. Multiple packages can be built from a single RPM spec file, if desired. RPM packages are created from RPM spec files using the rpmbuild tool.

Spec files are usually distributed within SRPM files, which contain the spec file packaged along with the source code.

SRPM

A typical RPM is pre-compiled software ready for direct installation. The corresponding source code can also be distributed. This is done in an SRPM, which also includes the "SPEC" file describing the software and how it is built. The SRPM also allows the user to compile, and perhaps modify, the code itself.

A software package could contain only platform independent scripts. In such a case, the developer could provide only an SRPM, which is still an installable RPM.

NOSRC

This is a special version of SRPM. It contains "SPEC" file and optionally patches, but does not include sources (usually because of license).

Forks

As of June 2010, there are two versions of RPM in development: one led by the Fedora Project and Red Hat, and the other by a separate group led by a previous maintainer of RPM, a former employee of Red Hat.

RPM.org

The rpm.org community's first major code revision was in July 2007; version 4.8 was released in January 2010, version 4.9 in March 2011, 4.10 in May 2012, 4.11 in January 2013, 4.12 in September 2014 and 4.13 in July 2015.

This version is used by distributions such as Fedora, Red Hat Enterprise Linux and derivatives, openSUSE, SUSE Linux Enterprise, Unity Linux, Mageia, OpenEmbedded, Tizen and OpenMandriva Lx (formerly Mandriva).

RPM v5

Jeff Johnson, the RPM maintainer since 1999, continued development efforts together with participants from several other distributions. RPM version 5 was released in May 2007.

This version is used by distributions such as Wind River Linux (until Wind River Linux 10), Rosa Linux, and OpenMandriva Lx (former Mandriva Linux which switched to rpm5 in 2011) and also by the OpenPKG project which provides packages for other common UNIX-platforms.

OpenMandriva Lx is going to switch back to rpm.org for 4.0 release.

OpenEmbedded, the last major user of RPM5, switched back to rpm.org due to issues in RPM5.

See also

• Autopackage — a "complementary" package management system
• Delta ISO — an ISO image which contains RPM Package Manager files
• dpkg — package management system used by Debian and its derivatives
• List of RPM-based Linux distributions
• pkg-config — queries libraries to compile software from its source code

References

• Schroeder, Jeff (30 January 2008). "Advanced RPM query strings". www.digitalprognosis.com. Archived from the original on 9 August 2011. Retrieved 28 March 2018.

External links

• RPM.org project home page
• RPM and DPKG command reference
• The story of RPM by Matt Frye in Red Hat Magazine Archived 2007-09-29 at the Wayback Machine
• How to create an RPM package
• Video tutorials for Building and Patching the RPMs
• RPM Notes - Building RPMs the easy way
• Packaging software with RPM, Part 1: Building and distributing packages
• Learn Linux, 101: RPM and YUM package management

Yashahime: Princess Half-Demon
Anime key visual
半妖の夜叉姫 (Han'yō no Yashahime)
Genre	Adventure, fantasy
Anime television series
Directed by	Teruo Sato
Written by	Katsuyuki Sumisawa
Music by	Kaoru Wada
Studio	Sunrise
Licensed by	NA: Viz Media SA/SEA: Medialink
Original network	NNS (ytv)
English network	SEA: Animax Asia
Original run	October 3, 2020 – present
Episodes	24

Yashahime: Princess Half-Demon (Japanese: 半妖の夜叉姫, Hepburn: Han'yō no Yashahime) is a Japanese anime television series produced by Sunrise. It is a sequel to the Inuyasha anime series, which itself is based on the original manga series written and illustrated by Rumiko Takahashi. It is the story of Towa Higurashi and Setsuna, Sesshomaru and Rin's twin daughters, and Moroha, Inuyasha and Kagome Higurashi's teenage daughter. The series aired from October 3, 2020 to March 20, 2021. A second season is set to premiere fall 2021.

Viz Media has licensed the series for North and Latin American territories, while Medialink has licensed it for Southeast Asian and South Asian territories.

Plot

See also: List of Inuyasha characters § Yashahime: Princess Half-Demon characters

Several years after the events of Inuyasha, Sesshomaru and Rin's daughter four-year-old Towa is separated from her twin sister Setsuna and gets stranded in the modern era, where she is adopted into her aunt Kagome Higurashi's family, raised by her younger brother Sota and his wife Moe.

One decade later, Towa is reunited with Setsuna, who came to the modern time through the vast power of the Sacred Tree of Ages. During their separation, Setsuna became a hardhearted demon-slayer working under Kohaku and does not remember her past as they and her dreams were stolen by the mythical Dream Butterfly. In order to restore them, the half-demon twins embark on an adventure while accompanied by their quarter-demon bounty hunter cousin Moroha, who is the feisty, hard-as-nails teenage daughter of Inuyasha and Kagome Higurashi, and also has no memory of her parents.

The spirit of the Sacred Tree of Ages reveals itself to the cousins, warning them that an old rival of their paternal dog-demon grandfather is planning on warping time since Sesshomaru refuses to fight him. At the same time, it is holding Rin in stasis for Sesshomaru because of her unusual connection to Lady Zero, the elder sister of Lord Kirinmaru, and creator of the seven mystical Rainbow Pearls, whose respective demonic powers equal those of the Shikon Jewel.

Release

See also: List of Yashahime: Princess Half-Demon episodes

The series was first announced in May 2020. It aired from October 3, 2020 to March 20, 2021 on Yomiuri TV and Nippon TV. The series was produced by Sunrise, directed by Teruo Sato with main character designs by Inuyasha original creator Rumiko Takahashi. Staff from Inuyasha returned, with Katsuyuki Sumisawa in charge of the scripts while Rumiko Takahashi acted as storyboard supervisor, Yoshihito Hishinuma in charge of the anime character designs and Kaoru Wada composing the music. The opening theme "New Era" is performed by the male idol group SixTONES, while the ending theme "Break" is performed by Uru. The second opening theme "Burn" is performed by NEWS, while the second ending theme "Kesshō" is performed by Ryokuōshoku Shakai.

Viz Media announced the rights to digital streaming, EST, and home video release of the series for North and Latin American territories. Medialink also announced that it has the rights to the series in Southeast Asian territories. Viz Media streamed the series on Crunchyroll, Funimation and Hulu. On October 26, 2020, Funimation announced a partnership with Viz Media to release an English dub of the series, with the English cast of Inuyasha reprising their roles. Funimation began streaming the English dub on November 6, 2020 along with Hulu and Crunchyroll.

On March 20, 2021, a second season of the series was announced following the release of Episode 24. The second season, titled Yashahime: Princess Half-Demon: The Second Act, will premiere fall, 2021.

Reception

James Beckett and Monique Thomas of Anime News Network listed Yashahime: Princess Half-Demon as one of the worst anime of the winter 2021 season.

External links

• Yashahime: Princess Half-Demon official website (in Japanese)
• Yashahime: Princess Half-Demon official website at Yomiuri TV (in Japanese)
• Yashahime: Princess Half-Demon official website at Aniplex (in Japanese)
• Yashahime: Princess Half-Demon official website at Viz Media
• 65.113.30.141 at Anime News Network's encyclopedia