All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Move IMAGE_BOOT stuff into distro's?
Date: Tue, 29 Dec 2009 19:46:05 +0100	[thread overview]
Message-ID: <hhdipd$25q$2@ger.gmane.org> (raw)
In-Reply-To: <c384c5ea0912290715l24b705fat6700077741b1cc5b@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29-12-09 16:15, Leon Woestenberg wrote:
> Why do we hardcode names of default packages in the "image.bbclass"?
> 
> Now every image recipe that doesn't want these has to know the
> variables it has to override.
> 
> Shouldn't this be distro material instead?

No, since these are things you want to be able to manage on a per image
basis, not distro wide. I don't want to create a whole 'new' distro just
to try mdev instead of udev or use tinylogin instead of shadow, etc.
When we made that change we discussed what the default values for those
vars should be and it was agreed they should provide sane defaults.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLOk5tMkyGM64RGpERAudNAJ4wC8aftgrdzk8BLa3FL2w7XC9l7wCfb9CN
2qCrG0DL86Qs+mPkB+yO9hE=
=+T+/
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2009-12-29 18:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 15:15 Move IMAGE_BOOT stuff into distro's? Leon Woestenberg
2009-12-29 15:34 ` Phil Blundell
2009-12-29 15:47   ` Leon Woestenberg
2009-12-29 18:46 ` Koen Kooi [this message]
2009-12-29 19:44   ` Leon Woestenberg
2009-12-29 22:42     ` Khem Raj
2009-12-30  8:48       ` Koen Kooi
2009-12-30  9:27         ` Frans Meulenbroeks
2009-12-30 19:37         ` Leon Woestenberg
2009-12-31 10:12           ` Frans Meulenbroeks

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='hhdipd$25q$2@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.