From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH] sysvinit: make pidof usuable in a standalone setting
Date: Tue, 31 May 2011 09:59:09 +0100 [thread overview]
Message-ID: <1306832349.27470.340.camel@rex> (raw)
In-Reply-To: <642CE635-2E68-4FE6-843D-A2104BED6CD4@dominion.thruhere.net>
On Tue, 2011-05-31 at 10:27 +0200, Koen Kooi wrote:
> No comments at all?
Patience ;-). It was a US/UK holiday yesterday and lots of people have
been taking a long weekend. Personally, whilst I did merge a few things
yesterday, this one didn't look that urgent so its on today's to look at
and reply to list.
> Op 28 mei 2011, om 13:21 heeft Koen Kooi het volgende geschreven:
>
> > Currently it's a symlink to killall5:
> >
> > $ dpkg-deb -c sysvinit-pidof_2.88dsf-r1_armv7a.ipk | grep pidof
> > lrwxrwxrwx root/root 0 2011-05-27 11:05 ./bin/pidof.sysvinit -> /sbin/killall5
> >
> > The point of the pidof subpackage was to have a pidof without
> needing sysvinit, this restores that behaviour. The trade-off is a
> 14KiB (armv7a, uncompressed) increase in size.
> >
> > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> > ---
> >
> > The alternative is to just move 'killall5' into the pidof subpackage and to RDPEPENDS_${PN} += "${PN}-pidof"
I think I prefer the alternative to duplicating binaries...
Cheers,
Richard
> > The change in this patch was the least amounts of edits to the recipe, let me know which way you prefer.
> >
> > meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb b/meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb
> > index 7d5e936..f0e73bb 100644
> > --- a/meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb
> > +++ b/meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb
> > @@ -5,7 +5,7 @@ SECTION = "base"
> > LICENSE = "GPLv2+"
> > LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
> > file://COPYRIGHT;endline=15;md5=349c872e0066155e1818b786938876a4"
> > -PR = "r1"
> > +PR = "r2"
> >
> > # USE_VT and SERIAL_CONSOLE are generally defined by the MACHINE .conf.
> > # Set PACKAGE_ARCH appropriately.
> > @@ -100,7 +100,7 @@ EOF
> > ln -s ../init.d/stop-bootlogd ${D}${sysconfdir}/rc$level.d/S99stop-bootlogd
> > done
> > mv ${D}${base_sbindir}/init ${D}${base_sbindir}/init.${PN}
> > - mv ${D}${base_bindir}/pidof ${D}${base_bindir}/pidof.${PN}
> > + cp ${D}${base_sbindir}/killall5 ${D}${base_bindir}/pidof.${PN}
> > mv ${D}${base_sbindir}/halt ${D}${base_sbindir}/halt.${PN}
> > mv ${D}${base_sbindir}/reboot ${D}${base_sbindir}/reboot.${PN}
> > mv ${D}${base_sbindir}/shutdown ${D}${base_sbindir}/shutdown.${PN}
> > --
> > 1.6.6.1
> >
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-05-31 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 11:21 [RFC][PATCH] sysvinit: make pidof usuable in a standalone setting Koen Kooi
2011-05-30 11:45 ` Koen Kooi
2011-05-31 8:27 ` Koen Kooi
2011-05-31 8:59 ` Richard Purdie [this message]
2011-05-31 9:27 ` Phil Blundell
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=1306832349.27470.340.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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.