From: Muhammad Shakeel <muhammad_shakeel@mentor.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] [v2] openssh: Enabling with systemd
Date: Mon, 15 Jul 2013 16:42:21 +0500 [thread overview]
Message-ID: <51E3E01D.9050905@mentor.com> (raw)
In-Reply-To: <CAJTo0LYmH8sDrpfYOhSd8WXKeoKGd-JiVu1EHMuj5vRLYBcxtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
On 07/12/2013 09:32 PM, Burton, Ross wrote:
> On 11 July 2013 19:32, Saul Wold <sgw@linux.intel.com> wrote:
>>> We are seeing different checks for different recipes. Do you
>>> guys think that it is possible to handle them in bbclass.
>>>
>> How different are they, there is the DISTRO_FEATURE check and then
>> typically the service file or the init file is sed'ed and
>> installed.
>
> My initial thoughts were to keep it simple and have a
> do_install_append() that deleted the sysvinit or systemd files
> depending on DISTRO_FEATURES, leaving installing the files themselves
> (from upstream, from a file, whatever) up to the recipe because
> that's where the complications are.
We can also easily move 'sed' part to systemd class because we will only be
looking for all the service files in ${systemd_unitdir}, irrespective of
how these got installed.
I gave a little thought to move the installation part into the class and
there
can be a solution but probably little complicated. The neatest solution
would
be to define an another variable say 'SYSTEMD_SERVICE_FILES_{PN}'
which will hold the name of all the service files, need to be installed,
along
with their relative path from WORKDIR. We can check in systemd class
that if
${systemd_unitdir} is not present, means upstream hasn't installed
anything,
then install whatever is in 'SYSTEMD_SERVICE_FILES_{PN}'.
Other option is to reuse current 'SYSTEMD_SERVICE_${PN}' that lists the
service
files in the package but doesn't include the path of service files. If
we do not
want a new variable, which seems like a duplication, then we can add the
path
with the service files in this variable and tweak systemd class to
handle this in
current implementation. We will add the path only if service file to be
installed is
not present in WORKDIR but buried somewhere in the package source.
Please let me know of your thoughts about installation part.
Best Regards,
Shakeel
[-- Attachment #2: Type: text/html, Size: 2802 bytes --]
next prev parent reply other threads:[~2013-07-15 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 7:45 [PATCH] [v2] openssh: Enabling with systemd Shakeel, Muhammad
2013-07-11 8:04 ` Muhammad Shakeel
2013-07-11 8:23 ` Martin Jansa
2013-07-11 9:55 ` Shakeel, Muhammad
2013-07-11 18:03 ` Saul Wold
2013-07-11 18:18 ` Ahsan, Noor
2013-07-11 18:32 ` Saul Wold
2013-07-12 16:32 ` Burton, Ross
2013-07-15 11:42 ` Muhammad Shakeel [this message]
2013-07-17 12:27 ` Burton, Ross
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=51E3E01D.9050905@mentor.com \
--to=muhammad_shakeel@mentor.com \
--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