From: Muhammad Shakeel <muhammad_shakeel@mentor.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] [v3] openssh: Add systemd support
Date: Tue, 20 Aug 2013 11:54:39 +0500 [thread overview]
Message-ID: <521312AF.3010504@mentor.com> (raw)
In-Reply-To: <5212876C.7080806@linux.intel.com>
On 08/20/2013 02:00 AM, Saul Wold wrote:
> On 08/18/2013 11:40 PM, Khem Raj wrote:
>> On Sun, Aug 18, 2013 at 11:18 PM, Muhammad Shakeel
>> <muhammad_shakeel@mentor.com> wrote:
>>> /usr/sbin/ is being sed'ed with ${sbindir} in do_install_append of the
>>> respective recipe file. /usr/bin/ and /bin/ is also taken care of.
>>
>> i see, thats better. however I do see a need to have a generalized
>> way of specifying service files and a generic
>> processing engine which then takes care of it. Otherwise we have the
>> same code replicated in multiple recipes
>
> Agreed, I think there should be a generalized solution here,
> implemented in the systemd.bbclass.
This is not required for all of the systemd unit files. Packages which
have upstream systemd support, e.g. avahi, ofono they install service
file theirselves.
I have already discussed to move this 'sed' part into systemd.bbclass
but Ross Burton had other ideas.
http://patches.openembedded.org/patch/53489/
So what is your final recommendation here?
> It also appears that this set is also creating a /lib dir that should
> not be there for non-systemd builds.
>
>> ERROR: Task 25
>> (/home/sgw/yocto/poky/meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb,
>> do_package) failed with exit code '1'
>> ERROR: QA Issue: nfs-utils: Files/directories were installed but not
>> shipped
>> /lib
>> ERROR: QA run found fatal errors. Please consider fixing them.
>> ERROR: Function failed: do_package_qa
>> ERROR: Logfile of failure stored in:
>> /home/sgw/yocto/builds/world/tmp/work/x86_64-poky-linux/nfs-utils/1.2.8-r0/temp/log.do_package.17558
Sorry about this error, I will fix this in next version.
Regards
--Shakeel
prev parent reply other threads:[~2013-08-20 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 17:27 [PATCH 1/4] [v3] openssh: Add systemd support Shakeel, Muhammad
2013-08-16 17:27 ` [PATCH 2/4] [v3] lighttpd: " Shakeel, Muhammad
2013-08-16 17:27 ` [PATCH 3/4] [v3] rpcbind: " Shakeel, Muhammad
2013-08-16 17:27 ` [PATCH 4/4] [v3] nfs-utils: " Shakeel, Muhammad
2013-08-16 17:47 ` [PATCH 1/4] [v3] openssh: " Khem Raj
2013-08-19 6:18 ` Muhammad Shakeel
2013-08-19 6:40 ` Khem Raj
2013-08-19 21:00 ` Saul Wold
2013-08-20 6:54 ` Muhammad Shakeel [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=521312AF.3010504@mentor.com \
--to=muhammad_shakeel@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.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