On 13:35 Sat 21 Aug , Sam Ravnborg wrote: > On Sat, Aug 21, 2010 at 12:27:34PM +0200, Sascha Hauer wrote: > > On Wed, Aug 18, 2010 at 05:15:36PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote: > > > On 06:17 Sun 08 Aug , Jean-Christophe PLAGNIOL-VILLARD wrote: > > > > this will add also the support of the new ncurse interface nconfig > > > > > > > > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@xxxxxxxxxxxx> > > > is it ok to apply it? > > > > Generally ok, yes. I just thought we should wait a little for a later > > version, or have I misunderstood Sam? > > Current state of kconfig in v2.6.36-rc1 (which is a later version than > the one Jean-Christophe references) is the following: > - savedefconfig bugs fixed > - reading a minimal config (created by savedefconfig) fixed > > The nconfig issues I mentioned regarding search are > not yet ready. > And I am not sure if they go in until next merge window. > > Likewise there are patches in the works that will ease > the integration with external projects. > The patches does the following: > - Allows the prefix to be configured (CONFIG_ => BR2_) > - No more hardcoded "kernel" strings > - mainmenu in the config file is used as headline > > These patches will go in during next merge window if they > are finished in due time. > > So all-in-all I would recommend to use kconfig from > v2.6.36-rc1 (rather than some random commit) and > then upgrade again around v2.6.37-rc1 time. ok I upgrade the patch and it will be good to update it regulary I will follow it is there a ML for Kconfig? Best Regards, J. _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
