From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] get minimal rootfs to be even smaller
Date: Tue, 11 Jun 2013 17:36:43 +0200 [thread overview]
Message-ID: <20130611153643.GG3233@jama> (raw)
In-Reply-To: <CAMKF1srGhvZLyhEZbYbFepZADbAKF1kJM2ObBEjc8OevQ5CCqQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
On Tue, Jun 11, 2013 at 08:22:27AM -0700, Khem Raj wrote:
> On Tue, Jun 11, 2013 at 8:03 AM, Phil Blundell <pb@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.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-06-11 15:36 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
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 [this message]
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=20130611153643.GG3233@jama \
--to=martin.jansa@gmail.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