RPM vs IPK
I know that historically Poky has used 'ipk' as the primary packaging mechanism. It seems that now Poky/Yocto has move to 'rpm'. My distribution is still using ipk, but I'm happy to change, given a good argument.
* Is there such [a good reason] to use rpm over ipk?
* What are the pros and cons? I'm mostly interested in very resource limited deeply embedded systems which often only run from FLASH.
Thanks for any comments
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 9 lines · Gary Thomas
I know that historically Poky has used 'ipk' as the primary packaging mechanism. It seems that now Poky/Yocto has move to 'rpm'. My distribution is still using ipk, but I'm happy to change, given a good argument.
* Is there such [a good reason] to use rpm over ipk?
* What are the pros and cons? I'm mostly interested in very resource limited deeply embedded systems which often only run from FLASH.Thanks for any comments
My advice is that for such a resource limited system, you're probably best of sticking to ipk, particularly if you have it working already.
opkg:
* Has a smaller disk footprint
* Is generally faster than rpm
rpm+zypper:
* More of an industry standard
* Emphasises correctness and robustness over speed (e.g. number of fsync calls)
* Has desktop/enterprise features
* Not optimised for size (e.g. uses c++)
I'd not say one was better than the other, they're just different and suit different use cases.
Cheers,
Richard
Quoted 16 lines · Richard Purdie
Quoted 9 lines · Gary Thomas
I know that historically Poky has used 'ipk' as the primary packaging mechanism. It seems that now Poky/Yocto has move to 'rpm'. My distribution is still using ipk, but I'm happy to change, given a good argument.
* Is there such [a good reason] to use rpm over ipk?
* What are the pros and cons? I'm mostly interested in very resource limited deeply embedded systems which often only run from FLASH.Thanks for any comments
My advice is that for such a resource limited system, you're probably best of sticking to ipk, particularly if you have it working already.
opkg:
Quoted 8 lines
* Has a smaller disk footprint
* Is generally faster than rpmrpm+zypper:
* More of an industry standard
* Emphasises correctness and robustness over speed (e.g. number of fsync calls)
Does this mean ipk/opkg fails along these lines in any way?
Quoted 1 line
* Has desktop/enterprise features
Such as?
Quoted 4 lines
* Not optimised for size (e.g. uses c++)
I'd not say one was better than the other, they're just different and suit different use cases.
Pretty much what I thought, thanks.
My only concern is that if rpm is the primary emphasis, ipk/opkg might suffer from rot.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 8 lines · Gary Thomas
Quoted 5 lines · Richard Purdie
rpm+zypper:
* More of an industry standard
* Emphasises correctness and robustness over speed (e.g. number of fsync calls)Does this mean ipk/opkg fails along these lines in any way?
The opkg source code has certainly not been audited as thoroughly as the rpm codebase for those kind of issues. I'd say the two codebases each have their own set of problems though :).
Quoted 1 line
Quoted 1 line
* Has desktop/enterprise features
Off the top of my head, the ones I'm aware of are:
Possibility of DeltaRPM updates
Various more advanced dependency calculations (which we're adding for the benefit of all packaging backends in Yocto)
* per-file dependenies
* perl/python module dependencies
* directory ownership
Multilib support
Tighter integration with features like prelink.
I'm sure some of the more rpm literate people on the list can detail others.
Quoted 9 lines
Quoted 4 lines
* Not optimised for size (e.g. uses c++)
I'd not say one was better than the other, they're just different and suit different use cases.
Pretty much what I thought, thanks.
My only concern is that if rpm is the primary emphasis, ipk/opkg might suffer from rot.
I want to see opkg continue to work well, if you do see any problems with it, let us know...
Cheers,
Richard
Quoted 8 lines · Richard Purdie
Quoted 7 lines · Gary Thomas
Quoted 5 lines · Richard Purdie
rpm+zypper:
* More of an industry standard
* Emphasises correctness and robustness over speed (e.g. number of fsync calls)
Quoted 5 lines
Quoted 1 line
Does this mean ipk/opkg fails along these lines in any way?
The opkg source code has certainly not been audited as thoroughly as the rpm codebase for those kind of issues. I'd say the two codebases each have their own set of problems though :).
From my recent experience with opkg, it appears that it's a very good packaging system for small to medium sized devices. It's small, efficient, but may not have all of the features needed in desktop/enterprise type designs.
I see RPM has very useful in medium to very large installations...
These two are very complementary within Yocto, and I expect it to stay that way.
Quoted 8 lines
Quoted 1 line
Quoted 1 line
* Has desktop/enterprise features
Off the top of my head, the ones I'm aware of are:
Possibility of DeltaRPM updates
Various more advanced dependency calculations (which we're adding for the benefit of all packaging backends in Yocto)
* per-file dependenies
This is something we enabled internally for all of the system to help develop tools overtime to discover and display dependency maps of not only recipes, or (run-time) packages, but of the files themselves.
Quoted 2 lines
* perl/python module dependencies
* directory ownership
RPM currently has directory ownership, but we do not use this in Yocto properly.
This will be something we'll hopefully be added in the near future. (Directory
ownership means specific package(s) and users/group/permissions are defined for packages. By default in most OE based systems it appears that the directories just end up being a by-product of the installation of files.. and the default 0755 root:root is set.)
Quoted 1 line
Multilib support
Multilib support is one of the key reasons we needed RPM support, and not just "rpm", but fully integrated rpm support.
The trick with multilib support is it's easy to have to packages, one that problems /lib/libfoo.so, and one that provides /lib64/libfoo.so. But what happens when there is a corresponding /bin/foo? Do you use alternatives, do use cause a fatal conflict that must be resolved by the packaging of the system? or in the case of RPM, do you use preprogrammed policy to either conflict -- or decide which of the two (or three) versions to use.
For larger systems, carrier grade specificall, the preprogrammed policy is the mechanism of choice for most installations.
Quoted 6 lines
Tighter integration with features like prelink.
I'm sure some of the more rpm literate people on the list can detail others.
Quoted 1 line
Quoted 1 line
* Not optimised for size (e.g. uses c++)
(Note, this is Zypper, not RPM.. RPM itself is written in C...)
Quoted 10 lines
Quoted 7 lines
Quoted 2 lines
I'd not say one was better than the other, they're just different and suit different use cases.
Pretty much what I thought, thanks.
My only concern is that if rpm is the primary emphasis, ipk/opkg might suffer from rot.
I want to see opkg continue to work well, if you do see any problems with it, let us know...
I have a vested interest in RPM, but I acknowledge that we need more then one packaging mechanism. RPM isn't the right answer for a lot of the devices people are producing.. neither is deb or ipk/opkg. (Deb support should work, but I'm pretty sure that is the least tested of what is supported in Yocto. It would be nice for someone familiar with the Debian packaging mechanisms to step up and help verify and improve the current implementation.)
--Mark
Quoted 9 lines
Cheers,
Richard
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Quoted 4 lines
My only concern is that if rpm is the primary emphasis, ipk/opkg might suffer from rot.
I think that wont be the case