Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Saul Wold <sgw@linux.intel.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 1/2] initscripts: split the functions script into a separate package
Date: Mon, 6 Jan 2014 15:29:17 +0800	[thread overview]
Message-ID: <52CA5B4D.6050206@windriver.com> (raw)
In-Reply-To: <52C72A60.9010702@linux.intel.com>

On 01/04/2014 05:23 AM, Saul Wold wrote:
> On 01/01/2014 06:25 PM, Chen Qi wrote:
>> Many SysV init scripts need the /etc/init.d/functions script. But
>> this script is part of the initscripts package. As a result, the
>> initscripts package should always be installed into the system to
>> avoid errors when starting daemons. However, it makes no sense to
>> install the initscripts package into a systemd based image, because
>> what the init scripts provide has already been provided by the systemd.
>> On the other hand, the functions script might be still needed in a
>> systemd based image because other init scripts such as distcc might need
>> it.
>>
>> The above situation leads to a natural separation of the functions 
>> script
>> from the initscripts package. And this patch does so. It separates the
>> functions script into initscripts-functions packages.
>>
>
> There seems to be a problem with the multi-lib build, please check 
> this logfile for errors.
>
> http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/71/steps/Building%20Images/logs/stdio 
>
>
> Thanks
>     Sau!
>
>

Thanks for pointing it out.

I've fixed it and sent out V3.
I also modified the patch a little so that it could apply to the latest 
master cleanly.

Best Regards,
Chen Qi

>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>>   meta/recipes-core/initscripts/initscripts_1.0.bb |    8 ++++++--
>>   1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/recipes-core/initscripts/initscripts_1.0.bb 
>> b/meta/recipes-core/initscripts/initscripts_1.0.bb
>> index 5951e0c..ea28672 100644
>> --- a/meta/recipes-core/initscripts/initscripts_1.0.bb
>> +++ b/meta/recipes-core/initscripts/initscripts_1.0.bb
>> @@ -42,8 +42,12 @@ KERNEL_VERSION = ""
>>   inherit update-alternatives
>>   DEPENDS_append = " update-rc.d-native"
>>
>> -ALTERNATIVE_PRIORITY = "90"
>> -ALTERNATIVE_${PN} = "functions"
>> +PACKAGES =+ "${PN}-functions"
>> +RDEPENDS_${PN} = "${PN}-functions"
>> +FILES_${PN}-functions = "${sysconfdir}/init.d/functions.${PN}"
>> +
>> +ALTERNATIVE_PRIORITY_${PN}-functions = "90"
>> +ALTERNATIVE_${PN}-functions = "functions"
>>   ALTERNATIVE_LINK_NAME[functions] = "${sysconfdir}/init.d/functions"
>>
>>   HALTARGS ?= "-d -f"
>>
>
>



  reply	other threads:[~2014-01-06  7:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02  2:25 [PATCH V2 0/2] Split the functions script into a separate package in initscripts Chen Qi
2014-01-02  2:25 ` [PATCH V2 1/2] initscripts: split the functions script into a separate package Chen Qi
2014-01-03 21:23   ` Saul Wold
2014-01-06  7:29     ` ChenQi [this message]
2014-01-02  2:25 ` [PATCH V2 2/2] Add missing RDEPENDS of initscripts-functions Chen Qi

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=52CA5B4D.6050206@windriver.com \
    --to=qi.chen@windriver.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