Best supported package manager?

Best supported package manager?

[Michael Davis]

[-- Attachment #1: Type: text/plain, Size: 185 bytes --]

Which package manager (ipk, rpm, deb) is best supported currently in poky?  I am wondering which manager is the most tested and stable?  I am building for the Zynq ZX3.  Thanks
-Mike

[-- Attachment #2: Type: text/html, Size: 1766 bytes --]

Re: Best supported package manager?

[Rudolf Streif]

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

> Which package manager (ipk, rpm, deb) is best supported currently in
poky?  I am wondering which manager is the most tested and stable?

RPM is the default package manager. I would expect that it has gotten the
most mileage so far because of that. All of them are tested with
autobuilder. IPK is probably the next commonly used one since popular for
embedded systems for its leightweight and smaller footprint design. You can
have YP build for any combination of the package managers at the same time.
The builds just take longer. I recommend starting with RPM and when your
system boots try out the other ones if you need to.

Rudi

[-- Attachment #2: Type: text/html, Size: 1103 bytes --]

Re: Best supported package manager?

[Michael Davis]

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

Cool, thanks for the info.  Just to be totally clear, when I specify say "package_ipk" what exactly does that mean for my build and resulting filesystem?  Does it mean that the entire filesystem is generated using ipk packages?  Does it mean that I will be able to use ipks in my resulting system?  Thanks again

-Mike

From: Rudolf Streif [mailto:rstreif@linuxfoundation.org]
Sent: Tuesday, October 08, 2013 1:10 PM
To: Michael Davis
Cc: poky@yoctoproject.org
Subject: Re: [poky] Best supported package manager?


> Which package manager (ipk, rpm, deb) is best supported currently in poky?  I am wondering which manager is the most tested and stable?

RPM is the default package manager. I would expect that it has gotten the most mileage so far because of that. All of them are tested with autobuilder. IPK is probably the next commonly used one since popular for embedded systems for its leightweight and smaller footprint design. You can have YP build for any combination of the package managers at the same time. The builds just take longer. I recommend starting with RPM and when your system boots try out the other ones if you need to.

Rudi

[-- Attachment #2: Type: text/html, Size: 3981 bytes --]

Re: Best supported package manager?

[Gary Thomas]

On 2013-10-08 14:09, Rudolf Streif wrote:
>
>>Which package manager (ipk, rpm, deb) is best supported currently in poky?  I am wondering which manager is the most tested and stable?
>
> RPM is the default package manager. I would expect that it has gotten the most mileage so far because of that. All of them are tested with autobuilder. IPK is probably the next
> commonly used one since popular for embedded systems for its leightweight and smaller footprint design. You can have YP build for any combination of the package managers at the
> same time. The builds just take longer. I recommend starting with RPM and when your system boots try out the other ones if you need to.

Actually, the package manager is a distribution choice and while
Poky might use RPM, many others use IPK.  Of course this is just
the default and depending on your distribution you may be able
to override that choice.

Each style of packaging has it's pros and cons (see the mailing
list archives) but for embedded systems IPK is a winner due to its
much lighter footprint (at least that's my experience).  Also note
that Poky (and OE in general) used IPK for much longer than they
have been using RPM which has only been in the past couple of years :-)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Best supported package manager?

[Rudolf Streif]

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

If you set

PACKAGE_CLASSES ?= "package_rpm"

that means that it will build RPM packages and will use them to build the
root file system.

If you set something like

PACKAGE_CLASSES ?= "package_rpm package_ipk"

it will build RPM and IPK packages and it will use RPM packages to build
the root file system. The first item listed in PACKAGE_CLASSES will be used
to build the root file system. If you want IPK to be used instead to build
your root file system:

PACKAGE_CLASSES ?= "package_ipk package_rpm"

Just setting PACKAGE_CLASSES does not include the package management system
into your root file system. You will have to add it via the
package-management feature:

EXTRA_IMAGE_FEATURES += "package-management"

:rjs

[-- Attachment #2: Type: text/html, Size: 1086 bytes --]