From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: "Burton\, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: RFE: make the init manager an image feature (again)
Date: Thu, 21 Feb 2013 11:34:44 +0100 [thread overview]
Message-ID: <lybobe0xbv.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CAJTo0LbAmTuj0dZKq7=wX5uqF9OV7dW7FXd4d2incdKSshXEmQ@mail.gmail.com> (Ross Burton's message of "Wed, 20 Feb 2013 19:58:28 +0000")
"Burton, Ross" <ross.burton@intel.com> writes:
>>> But it doesn't need to be as dangerous as binconfig.bbclass, because
>>> we already list .service or .socket files in SYSTEMD_SERVICE so we
>>> can improve that "find" call
>>
>> Why is 'find' required at all? afaik, only files from $SRC_URI are
>> affected. So we can
>>
>> 1. create an (overridable) SYSTEMD_EXTRA_SERVICES variable
>>
>> 2. fill this variable in systemd.bbclass with .service, .target, .socket
>> + .mount files from $SRC_URI
>>
>> 3. modify systemd's do_install so that files above are copied after
>> doing some some sanity checks (e.g. checks that no previous version
>> from 'make install' exists or that it are really systemd files).
>
> As I've said before you'll need to be pre-processing these files
> anyway,
oh... this means khem's "meta-systemd: Append ${PN} to SYSTEMD_SERVICE"
patch series is incomplete and all the do_install_append() need to get
yet more complicated....
It is really time, to move the additional-service-file installation back
into the class.
> so either the class gets *even more* logic or you just deal with it.
> Over time more and more upstreams will get systemd support so we'll
> be carrying overcomplicated logic for no reason. We're really just
> talking about one conditional and a sed call here.
By applying some general rules (e.g. using autoconf like '@bindir@'
templates), this can/should be done by the class and not in every
recipe.
Enrico
next prev parent reply other threads:[~2013-02-21 10:51 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 [this message]
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
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=lybobe0xbv.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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