On 13 August 2013 08:32, Laszlo Papp <[email protected]> wrote: > So, everyone suggested PACKAGECONFIG in here on the mailing list except Khem > whose reply I did not get. > > Yet, 4964 got closed by the "team". Could anyone please give a sane > description why and what would block the end users other than fork?
Quoting from comment 1 on 4964: """ Busybox is a rather complicated beast. PACKAGECONFIG is unfortunately not sufficient to manage it's config system. It is very similar to the Linux kernel config and we recently added configuration fragment support to busybox from the kernel recipes: commit 56dc1720caa48344238d352c7b6e9b0f0d41aa54 Author: Chen Qi <[email protected]> Date: Tue Feb 5 14:36:40 2013 +0800 busybox: add config fragments This allows you to use the default config and include only the delta in your layer's bbappend in the form of a config fragment added to the SRC_URI. """ If this isn't sufficient or is buggy, then fixing this is preferred (it works for the kernel, so should work for busybox). Ross _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
