Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On Mon, 2013-06-10 at 19:06 -0700, Khem Raj wrote: On May 31, 2013, at 7:11 AM, Marcin Juszkiewicz mar...@juszkiewicz.com.pl wrote: First hit: pci.ids.gz and usb.ids.gz ~350KB in total. udev just RRECOMMENDS usbutils-ids pciutils-ids so how did it get into build time dependencies to begin with ? Er, don't RRECOMMENDS always go into the build dependency list? p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On Tue, Jun 11, 2013 at 8:03 AM, Phil Blundell p...@pbcl.net wrote: Er, don't RRECOMMENDS always go into the build dependency list? if they do then whats the difference between DEPENDS and RRECOMMENDS functionally. since now rrecommended packages will always be available and they will always make into images. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On Tue, 2013-06-11 at 08:22 -0700, Khem Raj wrote: On Tue, Jun 11, 2013 at 8:03 AM, Phil Blundell p...@pbcl.net wrote: Er, don't RRECOMMENDS always go into the build dependency list? if they do then whats the difference between DEPENDS and RRECOMMENDS functionally. RDEPENDS are required and the package manager will insist they are always installed. RRECOMMENDS are optional; you can uninstall them after the fact, and you can (with some package managers at least) declare them to be BAD_RECOMMENDATIONS which will be ignored. since now rrecommended packages will always be available and they will always make into images. You say now, but as far as I know it has always been thus. If it wasn't then the set of packages that get installed in the image would depend on what things you happened to have lying around in your deploy directory, which would not be a very good thing. p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On Tue, Jun 11, 2013 at 08:22:27AM -0700, Khem Raj wrote: On Tue, Jun 11, 2013 at 8:03 AM, Phil Blundell p...@pbcl.net wrote: Er, don't RRECOMMENDS always go into the build dependency list? if they do then whats the difference between DEPENDS and RRECOMMENDS functionally. RDEPENDS and RRECOMMENDS right? since now rrecommended packages will always be available and they will always make into images. just the possibility to blacklist them with BAD_RECOMMENDATIONS. -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On Tue, Jun 11, 2013 at 8:26 AM, Phil Blundell p...@pbcl.net wrote: On Tue, 2013-06-11 at 08:22 -0700, Khem Raj wrote: On Tue, Jun 11, 2013 at 8:03 AM, Phil Blundell p...@pbcl.net wrote: Er, don't RRECOMMENDS always go into the build dependency list? if they do then whats the difference between DEPENDS and RRECOMMENDS functionally. RDEPENDS are required and the package manager will insist they are always installed. RRECOMMENDS are optional; you can uninstall them after the fact, and you can (with some package managers at least) declare them to be BAD_RECOMMENDATIONS which will be ignored. yeah now I see the code build is going to build RRECOMMENDS automatically hmm. Do BAD_RECOMMENDATIONS work with rpm ? since now rrecommended packages will always be available and they will always make into images. You say now, but as far as I know it has always been thus. If it wasn't then the set of packages that get installed in the image would depend on what things you happened to have lying around in your deploy directory, which would not be a very good thing. p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On Tue, 2013-06-11 at 08:40 -0700, Khem Raj wrote: yeah now I see the code build is going to build RRECOMMENDS automatically hmm. Do BAD_RECOMMENDATIONS work with rpm ? I think you mean with smart, and as far as I know the answer is no. p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On 11 June 2013 16:43, Phil Blundell p...@pbcl.net wrote: On Tue, 2013-06-11 at 08:40 -0700, Khem Raj wrote: yeah now I see the code build is going to build RRECOMMENDS automatically hmm. Do BAD_RECOMMENDATIONS work with rpm ? I think you mean with smart, and as far as I know the answer is no. Only rootfs_ipkg respects BAD_RECOMMENDATIONS: https://bugzilla.yoctoproject.org/show_bug.cgi?id=3916 -- bug for rpm https://bugzilla.yoctoproject.org/show_bug.cgi?id=4120 -- bug for dpkg Ross ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On May 31, 2013, at 7:11 AM, Marcin Juszkiewicz mar...@juszkiewicz.com.pl wrote: First hit: pci.ids.gz and usb.ids.gz ~350KB in total. udev just RRECOMMENDS usbutils-ids pciutils-ids so how did it get into build time dependencies to begin with ? ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On 06/10/2013 07:06 PM, Khem Raj wrote: On May 31, 2013, at 7:11 AM, Marcin Juszkiewicz mar...@juszkiewicz.com.pl wrote: First hit: pci.ids.gz and usb.ids.gz ~350KB in total. udev just RRECOMMENDS usbutils-ids pciutils-ids so how did it get into build time dependencies to begin with ? I looked into this a while back and it's the fact that those packages are built, so they are seen and get installed. If the packages aren't available they won't get installed. Since pciutils and usbutils are both DEPENDS of udev, those get built and the packages get deployed and then are available to be installed at the behest of the RRECOMMENDS. We could maybe have added BAD_RECOMMENDATIONS for core-image-minimal so that on a larger system udev would still have the -id files available, I just thought of this, not tested. Sau! ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [RFC] get minimal rootfs to be even smaller
I build core-image-minimal today and got 5.1MB image (AArch64/eglibc). Looked inside the image and found some extra files which can be dropped. First hit: pci.ids.gz and usb.ids.gz ~350KB in total. Normally they are needed for lspci/lsusb but they are brought by udev which does not need them. Next one can be ldconfig which is ~600KB. What do you think? ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
On Fri, 2013-05-31 at 16:11 +0200, Marcin Juszkiewicz wrote: Next one can be ldconfig which is ~600KB. There's already an option to turn that off: you can set USE_LDCONFIG=0 in your distro configuration (which micro does, for example). Converting that to be a modern DISTRO_FEATURE would be a fine thing. On the udev thing I guess my initial reaction would be that if you want the smallest rootfs you probably don't want to be using udev at all. But if it's installing files that are totally unnecessary then that does seem a bit extravagant and I agree that it should be curtailed. p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [RFC] get minimal rootfs to be even smaller
W dniu 31.05.2013 16:41, Phil Blundell pisze: On Fri, 2013-05-31 at 16:11 +0200, Marcin Juszkiewicz wrote: Next one can be ldconfig which is ~600KB. There's already an option to turn that off: you can set USE_LDCONFIG=0 in your distro configuration (which micro does, for example). Converting that to be a modern DISTRO_FEATURE would be a fine thing. Thanks for hint - may look at it next week. On the udev thing I guess my initial reaction would be that if you want the smallest rootfs you probably don't want to be using udev at all. I just wanted to have smallest possible image without doing any distro config changes. Think minimal image for testing KVM where KVM host rootfs can be built with same setup. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
