Re: trouble using a local kernel repo

[Bruce Ashfield <bruce.ashfield@windriver.com>]

On 12-02-16 06:18 PM, Hollis Blanchard wrote:
> On 02/16/2012 03:02 PM, Bruce Ashfield wrote:
>> That's the problem. I have a patch that detects this and abort is a non
>> bare upstream is used. I just need to send them .. which I'll do when
>> I get back to my desk next week.
>>
>> There are two reason for this bare clone requirement:
>>
>> - technical: this scales to several hundred branches. cloning, and
>> iterating
>> remote branches to create local tracking branches is noisy and
>> time consuming. So there's a trick that has been in use for years
>> that you can clone a bare upstream, and mass convert the branches
>> to local in a single operation.
>>
>> - social: you want to do your development in a different tree from the
>> one that is being cloned and used. That way the tree is clean, and you
>> are building what you expect.
>
> Do I want to do my development in a different tree? Are you sure? ;)

The point is that the tree is local to your machine, but it doesn't
have to be. You may only have push, not direct commit access. It's
really not asking for anything that isn't already common practice.

>
> I don't need to scale to hundreds of branches -- I just have one small
> patch I wanted to test. I already have it in a "clean" tree -- it's a
> committed changeset, with a commit message and everything, even though I
> haven't even been able to *test* it yet!

Right. I didn't imply that .. just to explain why it is like it is.

>
> I'm just trying to test a small kernel/meta patch, and the poorly
> documented list of setup requirements is growing longer and longer. All
> this stuff may be good practice for a more complicated scenario, but so
> far it seems like enormous overkill for my use case...

So why are you trying to use the technique ? Maybe the answer is that the
docs made it sound like this was the best/right way .. and that's a
problem in itself.

If you do have a single patch, toss it on the end of the SRC_URI and
everything just works like any other package.

The local repo instructions are largely for BSP developers or teams that
are working with the kernel on a more intensive basis. So there are some
setup requirements.

If you want to explore the git flow, and maintain out of tree branches,
repositories based on linux-yocto, etc. Then that's the time to kick
away on the git workflow and steps, but as the first plunge, it may not
be the right choice.

Cheers,

Bruce


>
> Hollis Blanchard
> Mentor Graphics, Embedded Systems Division
>