public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: RFE: make the init manager an image feature (again)
Date: Sun, 24 Feb 2013 10:37:26 +0000	[thread overview]
Message-ID: <E79C80CE9122499B9C7D2D855CDF6319@intel.com> (raw)
In-Reply-To: <CAJTo0LYo_FLTkZ_OiFf6Tt_oYO6NoUAUB74s__2UcKv7ccdxaA@mail.gmail.com>

Hi,

Just brainstorming out loud, but here's a suggestion that might just please everyone:

A virtual provider for the init manager, which can be overridden per-image (for main / rescue images).

DISTRO_FEATURES contains the init script *style* that you want: sysvinit or systemd.  These are not mutually exclusive so specifying both will get you both directly in packages that support both.  I'm still not convinced we need to split these out into separate packages, the size impact is practically negligible and the dependencies are effectively redundant as you'll have trouble booting without an init system.  Instead the postinsts should wrap the initscript fragments in checks.

Those distro features will also be used to enable/disable features in the source, so enabling systemd may well lead to libsystemd-* libraries sneaking into your rescue image.  The systemd libraries will have to be reviewed to verify that installing one of them doesn't pull in systemd itself.

Here's the fun bit - we can't have two builds of udev in the same distro, and that's what could happen, so I think we'll need to cut down to one udev instead of two.

I'm not entirely convinced this is a good plan yet myself though…

Ross



  parent reply	other threads:[~2013-02-24 10:53 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 18:19 RFE: make the init manager an image feature (again) Enrico Scholz
2013-02-15 18:47 ` Otavio Salvador
2013-02-15 23:44   ` Martin Jansa
2013-02-16  9:15 ` Richard Purdie
2013-02-16 10:47   ` Otavio Salvador
2013-02-16 12:53     ` Richard Purdie
2013-02-16 13:41       ` Otavio Salvador
2013-02-24  8:50         ` Khem Raj
2013-02-24 14:10           ` Otavio Salvador
2013-02-25 10:28           ` Enrico Scholz
2013-02-17 23:20       ` Martin Jansa
2013-02-18 10:17         ` Enrico Scholz
2013-02-20 19:58           ` Burton, Ross
2013-02-21 10:34             ` Enrico Scholz
2013-02-21 10:40               ` Burton, Ross
2013-02-21 11:34                 ` Enrico Scholz
2013-02-21 11:50                   ` Otavio Salvador
2013-02-21 12:01                     ` Phil Blundell
2013-02-16 11:57   ` Enrico Scholz
2013-02-16 12:34     ` Richard Purdie
2013-02-16 13:28       ` Otavio Salvador
2013-02-16 19:40       ` Martin Jansa
2013-02-16 19:49         ` Otavio Salvador
2013-02-17 13:06       ` Enrico Scholz
2013-02-21 15:35 ` Burton, Ross
2013-02-21 15:49   ` Otavio Salvador
2013-02-21 17:20   ` Enrico Scholz
2013-02-24 10:37   ` Ross Burton [this message]
2013-02-24 10:45     ` Ross Burton
2013-02-24 14:06     ` Otavio Salvador
2013-02-24 22:04       ` Ross Burton
2013-02-25  7:38         ` Martin Jansa
2013-02-25  7:46         ` Andreas Müller
2013-02-25 11:45         ` Otavio Salvador
2013-02-25 11:28     ` Enrico Scholz
2013-02-26  6:45     ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2013-02-16 20:20 Daniel Lazzari

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=E79C80CE9122499B9C7D2D855CDF6319@intel.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox