| Summary: | rpm 4 has a different set of subpackages then rpm 5 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Mark Hatle <mark.hatle> |
| Component: | core | Assignee: | Alexander Kanavin <alex.kanavin> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher, ngompa13, ross.burton |
| Version: | 2.3 | ||
| Target Milestone: | 2.3 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Mark Hatle
2017-03-15 21:42:59 UTC
BTW I'm in the process of determining how much space is saved by breaking the build components out into a sub package, for systems where they are not needed. Merged in oe-core 3b5ac72bdf76ac8ff98dc3c882a4edc77c6e2c33. I'm surprised you don't break things out as much. Both Fedora and Mageia have significant breakout of aspects of RPM into subpackages[1][2]. Depending on what kind of space or functional optimizations you're looking for, you may want to consider the Mageia approach or the Fedora one. I don't know much about how bitbake handles generating these separate things, but at least you can see the two strategies here. [1]: https://src.fedoraproject.org/cgit/rpms/rpm.git/tree/rpm.spec [2]: http://svnweb.mageia.org/packages/cauldron/rpm/current/SPECS/rpm.spec?view=markup |