Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: meta-systemd
Date: Fri, 18 May 2012 08:11:30 +0200	[thread overview]
Message-ID: <jp4p6i$h3t$1@dough.gmane.org> (raw)
In-Reply-To: <CALbNGRRGD=oykOV8mb0tTi+ZhHHTjsA7bbSTGSPr_OYUi=sPUQ@mail.gmail.com>

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

Op 17-05-12 22:18, Andreas Müller schreef:
> On Thu, May 17, 2012 at 9:41 PM, Koen Kooi <koen@dominion.thruhere.net>
> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Op 17-05-12 15:07, Andreas Müller schreef:
>>> Hi
>>> 
>>> happy to see this happen I have few questions on what is planned.
>>> 
>>> In README is written:
>>> 
>>>> And we're working to break the dependency on this one:
>>>> 
>>>> URI: git://git.openembedded.org/meta-openembedded
>>> 
>>> Maybe it is a misunderstanding but I would expect for contents of
>>> this layer
>>> 
>>> * systemd.bbclass * all from meta-oe/recipes-core/systemd * bbappends
>>> for all recipes with systemd support.
>>> 
>>> Is this correct?
>> 
>> Correct. The bbappends will likely cause dependencies on non-oecore
>> layers, but so be it. We might need to set the unbreak-me flag for
>> missing bb files that match our bbappends. Unless people actually start
>> reporting the bugs they encounter by including meta-oe...
> Two more questions:
> 
> 1. Has anybody patches in queue to fill meta-systemd? If not I would 
> stand up to prepare some.

The ones I had don't apply anymore.

> 2. Any complaints against the original idea to RRECOMMEND *-systemd 
> package as suggested [1] to avoid *-systemd packages in tasks/images. 
> AFAICR this was NAKed because a distro-var was necessary.

That's a statement, not a question :) I've been discussing this a lot the
past few months (conferences, irc, jabber) and I think we should have a
distro feature for every init system: sysvinit, systemd, upstart, openrc,
etc. I'm not sure if those would need to be mutually exclusive or not.

And finally: let's not make a lot of subpackages for things containing only
tmpfiles.d snippets. Consistency is good, but don't go overboard.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJPtegSAAoJEHZqAkdh1vT6dzAP/RQOOuxzgeZHOXpcKqBV+Qfz
GEbOMDdGN/kdvJk6hEEmVc3QnqtJmeyNW614xs0JQPDJMTOcMQ5OJT35qhPOkq5y
TxRJ1A1R/IbFmtQnhwkltkIeMfqeXo1PasiZGXc+ebbrHrtVDqI2Dl1Mb3HjrOup
rzLXQ6JEwYOY/agsHHGncKz/wjEhh9hW1nF24F/APHd1qcHHESx9LS9hV2fSbZDv
TJvzQMznN5Jiw3TomgdCrGpMI+oSjYY0aUugqUNkEor766pyhalMumqVBbHLEqyx
bSRCTChSKDv/txdjGetx46iwd4LI3BXsczxqewAWGxG9QoLMV6fSmRs0TDwItjbL
0VqbM9qY1AHLvXOVjzJrh3ds7i02iFsP9ffT+5dDFArYik7eZmkhJMlTVKC+UMjL
t+pVEvIJasFpZZ36jOxdzRTpD1qZa/5qBpS9hENbyXzMZDyYVsc4m1EObMXzBQvX
QRjwBNNXbuLufHWIi4oPd8YNyoqgP9CiakLFT2AtHnFb8n5PcNTHdPUAlYFrdx7U
Nmo4u5zjLmKkjKViujjvKGxvJPKw5KIiPyNlnDiDZtgLgdHlal51YRFLHKYhiHXK
A7YPcNhvv+V4RhDUxzXHkZ35mCKaTDIXP1/MdxIYiIQgkAe8FCrAkn+/xhu/x4hZ
/TJNHwWLO1tTym+l4KEj
=mMlk
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2012-05-18  6:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 13:07 meta-systemd Andreas Müller
2012-05-17 19:41 ` meta-systemd Koen Kooi
2012-05-17 20:18   ` meta-systemd Andreas Müller
2012-05-17 23:23     ` meta-systemd Denys Dmytriyenko
2012-05-18  4:28       ` meta-systemd Denys Dmytriyenko
2012-05-18  6:05         ` meta-systemd Koen Kooi
2012-05-18  6:11     ` Koen Kooi [this message]
2012-06-07 18:27   ` meta-systemd Andreas Müller
2012-06-08  5:47     ` meta-systemd Koen Kooi

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='jp4p6i$h3t$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox