From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: busybox & syslog init script
Date: Wed, 03 Jun 2009 10:54:00 -0400 [thread overview]
Message-ID: <4A268E88.1030605@cbnco.com> (raw)
In-Reply-To: <1244038988.2611.73.camel@mill.internal.reciva.com>
Phil Blundell wrote:
> On Wed, 2009-06-03 at 10:09 -0400, Michael Smith wrote:
>> I'd prefer RRECOMMENDS to RDEPENDS, because if I don't have
>> CONFIG_SYSLOGD=y, I can make busybox-syslog be empty so it won't get
>> created and nothing will complain.
> RRECOMMENDS would work, but ipkg will issue an ugly diagnostic
> ("unsatisfied recommendation for...") if busybox-syslog is missing. I'm
> not sure what other package managers will do here.
Yeah, me neither. I can say Busybox dpkg doesn't grok Recommends (or
dependencies, as far as I know :)
apt-get (used in rootfs_deb) doesn't seem to print a warning when the
recommended package is missing.
I'm reluctant to use RDEPENDS because for other, similar packages in the
recipe (e.g. busybox-mdev), the dependency goes in the opposite
direction: busybox-mdev depends on busybox.
> It might be better to stick with RDEPENDS and either (i) arrange for the
> dependency to be conditional on CONFIG_SYSLOGD having been enabled,
> which you could do with a bit of python in busybox.bb,
I was thinking about this and I'm not sure how to get the python bit to
run after do_fetch (so defconfig is available in ${WORKDIR}). It's
probably possible but it would take quite a bit of fiddling, and would
only save an ipkg warning for the few of us who don't set
CONFIG_SYSLOGD=y. Currently, all in-tree configs set CONFIG_SYSLOGD.
Mike
next prev parent reply other threads:[~2009-06-03 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 1:27 busybox & syslog init script Michael Smith
2009-06-03 9:49 ` Phil Blundell
2009-06-03 14:09 ` Michael Smith
2009-06-03 14:23 ` Phil Blundell
2009-06-03 14:54 ` Michael Smith [this message]
2009-06-03 15:16 ` Phil Blundell
2009-06-03 17:01 ` Otavio Salvador
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=4A268E88.1030605@cbnco.com \
--to=msmith@cbnco.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.