On 12/18/2014 02:30 PM, Burton, Ross wrote:
On 18 December 2014 at 06:23, Mike Looijmans <[email protected] <mailto:[email protected]>> wrote: Putting the script into its own package is no problem, but how does one arrange this with mdev.conf? That's a fairly good argument for keeping it in the same package, and we can expect that users of mdev will be providing their own configuration file anyway.
Indeed. I was just implementing the split up, but it looks weird. You end up with a package "busybox-mdev" that contains nothing but an initscript and a config file (because the actual "mdev" binary is supplied by busybox), which refers to scripts that don't exist, and then an extra busybox-mdev-extraconf that supplies these scripts, but doesn't actually contain any configuration files in spite of its name. And then I had to find a way to get this package installed by default, which also isn't trivial.
So can we keep it al in busybox-mdev? It's a tiny config package anyway, and when providing private configs (which should rarely be needed now), it's easy enough to replace these in a bbappend.
M. Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Systems Eindhovenseweg 32-C, NL-5683 KH Best Postbus 440, NL-5680 AK Best Telefoon: (+31) (0) 499 33 69 79 Telefax: (+31) (0) 499 33 69 70 E-mail: [email protected] Website: www.topic.nl Please consider the environment before printing this e-mail Topic zoekt gedreven (embedded) software specialisten! http://topic.nl/vacatures/topic-zoekt-software-engineers/ -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
