public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: RFE: make the init manager an image feature (again)
Date: Sat, 16 Feb 2013 12:57:50 +0100	[thread overview]
Message-ID: <lyhalcmpxd.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1361006114.31795.19.camel@ted> (Richard Purdie's message of "Sat, 16 Feb 2013 09:15:14 +0000")

Richard Purdie <richard.purdie@linuxfoundation.org> writes:

>> it would be nice when the decision to make the init manager a distribution
>> feature will be reverted to the old oe-meta mechanism.
>
> The trouble is that by making it an "image feature", people will
> expect *everything* to work properly and to be able to have fully
> functional sysvinit and systemd variants of images.

I do not see an obvious reason why fully functional sysvinit, systemd and
perhaps upstart image variants based on the same distribution/package set
are impossible.

Of course, not "everything" will work.  But initmgr being a distribution
feature makes some things completely impossible.


> We already see this expectation.

IMO, removal of features just to lower expectations is the completely
wrong way.


> Trying to explain to people what the limitations are, what is expected
> to work and what isn't will be difficult.

OpenEmbedded is not an end-user distribution but for people who are
willing to invest some learning effort.  Trying to limit ourself on the
lowest common ground is not desirable imo.


> For that reason I'd rather see this done in a different way, for
> example blacklisting the problematic systemd dependencies at image
> generation time with some kind of stronger BAD_RECOMMENDS code.

Assuming we are able to break the hard dependencies, what is with package
scripts which require programs, files or directories from these deps?  Do
we need a way to differ between good and bad script failures then?

Sounds extremely hacky and fragile...


Enrico



  parent reply	other threads:[~2013-02-16 12:14 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 [this message]
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
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=lyhalcmpxd.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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