From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3 2/2] Add missing RDEPENDS of initscripts-functions
Date: Fri, 17 Jan 2014 16:37:40 +0100 [thread overview]
Message-ID: <20140117153740.GN3742@jama> (raw)
In-Reply-To: <66190526.u9bvojJavk@peggleto-mobl5.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2461 bytes --]
On Fri, Jan 17, 2014 at 02:11:39PM +0000, Paul Eggleton wrote:
> Hi Qi,
>
> On Monday 06 January 2014 15:27:35 Chen Qi wrote:
> > Now that the initscripts-functions has been packaged separately,
> > packages which may use the functions script should have a runtime
> > dependency on it.
> >
> > Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> > ---
> > meta/recipes-bsp/alsa-state/alsa-state.bb | 2 +-
> > meta/recipes-bsp/apmd/apmd_3.2.2-14.bb | 1 +
> > .../irda-utils/irda-utils_0.9.18.bb | 2 ++
> > .../nfs-utils/nfs-utils_1.2.9.bb | 4 ++--
> > meta/recipes-connectivity/openssh/openssh_6.4p1.bb | 2 +-
> > meta/recipes-connectivity/ppp/ppp_2.4.5.bb | 1 +
> > meta/recipes-core/dbus/dbus.inc | 2 +-
> > meta/recipes-core/systemd/systemd_208.bb | 2 +-
> > meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 2 +-
> > meta/recipes-devtools/distcc/distcc_3.1.bb | 1 +
> > meta/recipes-devtools/tcf-agent/tcf-agent_git.bb | 2 +-
> > meta/recipes-extended/at/at_3.1.14.bb | 3 +--
> > meta/recipes-extended/cronie/cronie_1.4.11.bb | 2 ++
> > meta/recipes-extended/rpcbind/rpcbind_0.2.1.bb | 2 ++
> > meta/recipes-extended/sysklogd/sysklogd.inc | 2 ++
> > meta/recipes-extended/xinetd/xinetd_2.3.15.bb | 1 +
> > .../oprofile/oprofileui-server_git.bb | 2 +-
> > 17 files changed, 22 insertions(+), 11 deletions(-)
>
> Sorry to come back on this patchset again, but could we not detect
> installation of an initscript requiring these functions in update-rc.d.bbclass
> and just add the RDEPENDS automatically? Otherwise it's just another thing
> people can get wrong when writing a recipe, not to mention all of the existing
> recipes outside OE-Core that install initscripts.
Agreed, my current list of components where I've reverted this (to get
my images building again) is:
dbus, systemd, apmd, rpcbind, nfs-utils, alsa-state, openssh, ppp,
cronie, irda-utils
To be fair, it's possible that some of these need it and I just don't
use their script in runtime (e.g. irda-utils is included only in image
on "spitz" MACHINE and I've never used irda here - it's pulled through
some packagegroup because MACHINE_FEATURES have irda)
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-01-17 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 7:27 [PATCH V3 0/2] Split the functions script into a separate package in initscripts Chen Qi
2014-01-06 7:27 ` [PATCH V3 1/2] initscripts: split the functions script into a separate package Chen Qi
2014-01-06 7:27 ` [PATCH V3 2/2] Add missing RDEPENDS of initscripts-functions Chen Qi
2014-01-17 14:11 ` Paul Eggleton
2014-01-17 15:37 ` Martin Jansa [this message]
2014-01-20 2:15 ` ChenQi
2014-01-20 10:18 ` Martin Jansa
2014-01-23 12:14 ` ChenQi
2014-01-20 2:12 ` ChenQi
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=20140117153740.GN3742@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@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