From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: meta-systemd
Date: Fri, 08 Jun 2012 07:47:39 +0200 [thread overview]
Message-ID: <jqs3lq$bpg$1@dough.gmane.org> (raw)
In-Reply-To: <CALbNGRSDJGWyQd0ZwASa4ZrJ9FfD=y08ET_gg-xStbpLGtnQBw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 07-06-12 20:27, 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.
>
> I started with meta-systemd and want to do some testing. The mentioned
> 'unbreak-me' - is it available already or and idea to be implemented?
BB_DANGLINGAPPENDS_WARNONLY = "true"
in the layer.conf should work.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJP0ZH7AAoJEHZqAkdh1vT6eaoP/0J5NvTCFHuAO7aIr6K6rCdx
1aAgsq764gW2FhUg0xUwdqkcRzBDxD+KRF0uYDFhltsT0scMC6/V91NYbzk6Bi8x
sHe7pcmnQBVJaIAe4Y54gbXjFP838g044ypjNLvwGe4fPSWkdNWZ+mU5lUKj2PQY
Hwa6RpRLXRrAJLBAmElWQ3ULTX0q2tho91KK69EmSiqD5Wj/ql9plO72KzX191uf
l0lPdK0WE86fpGn6QbJaDN7Q9gH1RoazYxqUwA23P8ZZ3k+JHZy4eqWIn1HWTouO
bK3e5rKfNm5SiGhjw3Y5WQvyiv/4w4obsPNTUJrXGP6tNkx5Kx/T31VsWLtik+oR
tXxcQEnkkMVafy8J//tQTtdoDDG/Igyvsw+W/czViWs7AK40WpElClUDTes8AOoz
YSJZlYgGYykqYb50imdm+RlSMovn5cLoTivYGz3GBqgpsBkatRWFb+EUfW3Knxz/
Iosy045Eho8/5z4hhwsggltkJxg5VkEup4h0rN1NRSQis70U+PJ7CTO6/+6959gQ
s3wSbVjsc7Qnw6FJhfYRdtlDZcxd6tHi/5Rqe5frQ1zdCDNZHJRxtOXsrjF2qh2r
qdnNcB/PgF9c03VKfBouP83VC0LoOzHZklG2XkAngZd4CcZuxyhTp0DLdns14IlL
vFvtzPj1yXUdYVHzEWlN
=n4Hr
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-06-08 5:58 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 ` meta-systemd Koen Kooi
2012-06-07 18:27 ` meta-systemd Andreas Müller
2012-06-08 5:47 ` Koen Kooi [this message]
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='jqs3lq$bpg$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 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.