Re: [PATCH 00/15] devtool and externalsrc improvements

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2015-02-19 at 16:55 +0000, Paul Eggleton wrote:
> On Thursday 19 February 2015 11:47:01 Bruce Ashfield wrote:
> > On Thu, Feb 19, 2015 at 11:39 AM, Paul Eggleton
> > <paul.eggleton@linux.intel.com> wrote:
> > > I've been attempting to enable usage of devtool with the kernel (which
> > > effectively means using the externalsrc class with the kernel). This
> > > doesn't really work yet due to lack of handling the kernel configuration,
> > 
> > I've always insisted/argued and designed in that externalsrc shouldn't touch
> > the kernel configuration at all.
> > 
> > You are building a tree that is completely managed outside of the build
> > system, and getting the kernel configuration in place is part of that
> > management.
> > 
> > So I'm not convinced it is a problem that needs to be solved.
> 
> So, externalsrc still doesn't touch the configuration, and it is not my plan to 
> make it do so. However, users do need some way of setting up that configuration 
> when checking out those sources for the first time, and if that's to be of any 
> use to someone who just wants to make some minor changes, it should be the 
> exact same configuration you get when you build the recipe as normal. That is 
> what I believe "devtool modify" (at least with -x) should be doing, given that 
> it is one means you can use to set up a development environment if you do not 
> have one already.
> 
> We can certainly talk about the mechanism and work out the best way to do it, 
> such that it fits in with how linux-yocto works and meets user expectations. My 
> intent with this series was to get us to the point where we can at least 
> experiment and have that discussion.

Having the option of triggering the standard configuration process as
per a usual linux-yocto build but on an external direction, standalone
may be the best option?

Cheers,

Richard