Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kang Kai <kai.kang@windriver.com>
To: <sgw@linux.intel.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Fix lsbinitscripts link problem
Date: Thu, 28 Jun 2012 17:35:55 +0800	[thread overview]
Message-ID: <cover.1340873279.git.kai.kang@windriver.com> (raw)

Hi Saul,

I update the initscripts to use update alternative way to install file functions.
That make file functions provided by lsbinitscripts will be used instead of initscripts.

Regards,
Kai

The following changes since commit 8ce8d25bcda0e2e0b62204d5ca5875dedcaacf7d:

  sanity.bbclass: Increase LAYER_CONF_VERSION to match bblayers change (2012-06-25 17:20:54 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib kangkai/distro
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/distro

Kang Kai (1):
  initscripts: use update-alternative to handle file functions

Xiaofeng Yan (1):
  lsbinitscripts: Add a linking for functions.lsbinitscripts

 meta/recipes-core/initscripts/initscripts_1.0.bb |   10 ++++++++--
 meta/recipes-extended/lsb/lsbinitscripts_9.03.bb |    6 +++---
 2 files changed, 11 insertions(+), 5 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2012-06-28  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  9:35 Kang Kai [this message]
2012-06-28  9:35 ` [PATCH 1/2] initscripts: use update-alternative to handle file functions Kang Kai
2012-07-03 13:53   ` Richard Purdie
2012-06-28  9:35 ` [PATCH 2/2] lsbinitscripts: Add a linking for functions.lsbinitscripts Kang Kai
2012-07-07  0:43   ` Saul Wold
2012-07-09  1:33     ` Kang Kai
2012-07-03  1:42 ` [PATCH 0/2] Fix lsbinitscripts link problem Kang Kai
2012-07-03  4:04   ` Saul Wold
2012-07-03  5:49     ` Kang Kai

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=cover.1340873279.git.kai.kang@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=Zhenfeng.Zhao@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