From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] get minimal rootfs to be even smaller
Date: Mon, 10 Jun 2013 21:27:26 -0700 [thread overview]
Message-ID: <51B6A72E.5080008@linux.intel.com> (raw)
In-Reply-To: <E947360C-AE06-42E4-AD51-2DA926D1448D@gmail.com>
On 06/10/2013 07:06 PM, Khem Raj wrote:
>
> On May 31, 2013, at 7:11 AM, Marcin Juszkiewicz <marcin@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
>
>
next prev parent reply other threads:[~2013-06-11 4:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 14:11 [RFC] get minimal rootfs to be even smaller Marcin Juszkiewicz
2013-05-31 14:11 ` [PATCH] udev: do not recommend pciutils/usbutils ids Marcin Juszkiewicz
2013-05-31 14:50 ` Burton, Ross
2013-05-31 14:41 ` [RFC] get minimal rootfs to be even smaller Phil Blundell
2013-05-31 15:24 ` Marcin Juszkiewicz
2013-06-11 2:06 ` Khem Raj
2013-06-11 4:27 ` Saul Wold [this message]
2013-06-11 15:03 ` Phil Blundell
2013-06-11 15:22 ` Khem Raj
2013-06-11 15:26 ` Phil Blundell
2013-06-11 15:40 ` Khem Raj
2013-06-11 15:43 ` Phil Blundell
2013-06-11 15:55 ` Burton, Ross
2013-06-11 15:36 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51B6A72E.5080008@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox