[OE-core] [PATCH 5/5] busybox.inc: Install hwclock init script only if rtc is present in MACHINE_FEATURES

Martin Jansa martin.jansa at gmail.com
Wed Jul 11 09:11:37 UTC 2012


On Tue, Jul 10, 2012 at 11:43:58PM +0100, Phil Blundell wrote:
> On Wed, 2012-07-11 at 01:15 +0300, Andrei Gherzan wrote:
> > And to move a little further, busybox should be configured with
> > CONFIG_HWCLOCK=y only if it makes sense for that MACHINE. In my
> > opinion this is machine specific. 
> 
> That's a DISTRO decision.  I suspect most that have binary feeds would
> prefer to have a single busybox binary per architecture, and accept the
> few wasted bytes on machines without RTC, than to make it MACHINE
> specific and end up building it multiple times.

Agreed.

It would be better to package initscript + hwclock to separate packages
and then pull it to image only for machines with RTC.. but not making
whole busybox machine specific.

Another advantage of this would be option to use busybox-hwclock as utility
and hwclock-systemd instead of busybox-hwclock-init for images which are
using systemd.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120711/36ca808c/attachment-0002.sig>


More information about the Openembedded-core mailing list