On 09/21/2011 08:18 AM, John Stultz wrote: > On Wed, 2011-09-21 at 08:44 +0200, Richard Cochran wrote: >> On Tue, Sep 20, 2011 at 10:22:41PM -0700, John Stultz wrote: >>> After noticing almost every distro has their own method of managing >>> config fragments, I went looking at some best practices, and wanted >>> to try to consolidate some of the different approaches so this fairly >>> simple infrastructure can be shared (and new distros/build systems >>> don't have to implement yet another config fragment merge script). >> >> John, >> >> I have been wanting to make or find a way to start with an allnoconfig >> and enable a short list of config options (and the options that are >> needed to allow them). I don't want the other defaults at all. > > "make oldnoconfig" provides something close to this, I think. > >> Can I use your script for this? If not, is there another way to go >> about it? > > I guess my script could take an option to use oldnoconfig instead of the > alldefconfig method. I had considered suggesting this as well. It would be useful for assembling a bare minimum configuration. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
