From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: busybox & syslog init script
Date: Wed, 03 Jun 2009 10:49:17 +0100 [thread overview]
Message-ID: <1244022557.2611.14.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906022113520.27204@juice.ott.cti.com>
On Tue, 2009-06-02 at 21:27 -0400, Michael Smith wrote:
> 1) split the syslog initscript into busybox-syslog, as is already done for
> busybox-httpd and busybox-udhcpd;
> 2) or, manually handle the stuff the update-rc.d class would normally take
> care of for busybox, so the syslog initscript stays in the busybox
> package.
>
> I'd prefer #1, but I don't think I could ever track down all the in-tree
> and out-of-tree images that depend on busybox, and add "busybox-syslog" to
> all of them. I guess I'll try #2. Just checking if someone has a better
> idea.
The only practical way to do #1 is to make busybox Depend: on the
newly-created busybox-syslog package. Otherwise, folks who do "ipkg
install busybox" in the expectation of getting the syslog bits will be
disappointed. This means that there's no need to root out all the
images and add busybox-syslog explicitly; it'll be pulled in
automatically when the images are created.
If that works for you then I think you might as well go ahead and do #1.
Otherwise, yes, I agree that #2 sounds like the only other viable
option.
p.
next prev parent reply other threads:[~2009-06-03 9:58 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 [this message]
2009-06-03 14:09 ` Michael Smith
2009-06-03 14:23 ` Phil Blundell
2009-06-03 14:54 ` Michael Smith
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=1244022557.2611.14.camel@mill.internal.reciva.com \
--to=pb@reciva.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.