From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] removing DISTRO_* vars from task-boot
Date: Thu, 19 Feb 2009 12:14:18 +0100 [thread overview]
Message-ID: <gnjeua$b0f$1@ger.gmane.org> (raw)
In-Reply-To: <gnjcun$429$1@ger.gmane.org>
On 19-02-09 11:40, Koen Kooi wrote:
> On 18-02-09 20:22, Tom Rini wrote:
>> On Wed, Feb 18, 2009 at 07:43:42PM +0100, Koen Kooi wrote:
>>> On 17-02-09 17:35, Tom Rini wrote:
>>>> On Tue, Feb 17, 2009 at 01:26:34PM +0100, Koen Kooi wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Lately I have been wondering how to change the /dev manager on a per
>>>>> image base, since I want udev for most images and busybox-mdev for
>>>>> special-purpose stuff. The catch is that I want to keep using
>>>>> task-boot
>>>>> for both.
>>>>>
>>>>> Currently we have:
>>>>>
>>>>> DISTRO_DEV_MANAGER ?= "${@base_contains("MACHINE_FEATURES",
>>>>> "kernel26",
>>>>> "udev","",d)}"
>>>>> DISTRO_INIT_MANAGER ?= "sysvinit sysvinit-pidof"
>>>>> DISTRO_INITSCRIPTS ?= "initscripts"
>>>>> DISTRO_LOGIN_MANAGER ?= "tinylogin"
>>>>>
>>>>> in task-boot.bb
>>>>>
>>>>> There are various ways we could attack this:
>>>>>
>>>>> 1) The image.bbclass way:
>>>>>
>>>>> Put the following in image.bbclass:
>>>>>
>>>>> IMAGE_DEV_MANAGER ?= "${@base_contains("MACHINE_FEATURES", "kernel26",
>>>>> "udev","",d)}"
>>>>> IMAGE_INIT_MANAGER ?= "sysvinit sysvinit-pidof"
>>>>> IMAGE_INITSCRIPTS ?= "initscripts"
>>>>> IMAGE_LOGIN_MANAGER ?= "tinylogin"
>>>>>
>>>>> Pros:
>>>>> * Takes immediate effect
>>>>> * Can have distro defaults, overridable per image
>>>>>
>>>>> Cons:
>>>>> * marks them as 'user installed'
>>>>> * you can't 'debootstrap' from tasks anymore, you need to encode
>>>>> knowledge about the above vars into the debootstrap script
>>>> I really like this one as for our uses there's times where I'd rather
>>>> let busybox handle INIT_MANAGER and LOGIN_MANAGER too.
>>> Philip C. agrees with you. Should be move everything over or start with
>>> IMAGE_DEV_MANAGER?
>>
>> I say do it all now. Flexibility is good, lets get it done.
>
> The patch should appear on this ml right about now.
Mailman seems to hate me:
http://amethyst.openembedded.net/~koen/0001-task-boot-rename-DISTRO_-vars-to-IMAGE_-vars-and-mo.patch
next prev parent reply other threads:[~2009-02-19 11:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 12:26 [RFC] removing DISTRO_* vars from task-boot Koen Kooi
2009-02-17 16:35 ` Tom Rini
2009-02-18 18:43 ` Koen Kooi
2009-02-18 19:22 ` Tom Rini
2009-02-19 10:40 ` Koen Kooi
2009-02-19 11:00 ` Sledz, Steffen
2009-02-19 11:26 ` Koen Kooi
2009-02-19 12:17 ` Sledz, Steffen
2009-02-19 11:14 ` Koen Kooi [this message]
2009-02-19 12:51 ` Marcin Juszkiewicz
2009-02-18 20:07 ` Philip Balister
2009-02-19 11:08 ` Marcin Juszkiewicz
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='gnjeua$b0f$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.