SRCREV for BBLAYERS

SRCREV for BBLAYERS

[Richard Leitner - SKIDATA]

Hi,
I've a question regarding the BBLAYERS variable.
Is it possible to set some kind of a SRCREV (=> git tag/branch/commit-id) for a path listed in BBLAYERS?

I came to this question because I've two different branches in my meta layer: one for development and one for 'stable' releases.
Therefore I have also two different build dirs and want to 'pin' the branches/tags to the build dir (preferable via the bblayers.conf).
I think this should be possible because at the start of a build the revs are displayed like: meta-yocto = "[branch]:[commit-id]"
The problem is that I wasn't able to find any answers or solutions on the web so I ask you now for help.

I'd appreciate any kind of help!
Thanks!

best regards,
Richard

Re: SRCREV for BBLAYERS

[Paul Eggleton]

Hi Richard,

On Monday 03 February 2014 12:17:04 Richard Leitner - SKIDATA wrote:
> I've a question regarding the BBLAYERS variable.
> Is it possible to set some kind of a SRCREV (=> git tag/branch/commit-id)
> for a path listed in BBLAYERS?
> 
> I came to this question because I've two different branches in my meta
> layer: one for development and one for 'stable' releases. Therefore I have
> also two different build dirs and want to 'pin' the branches/tags to the
> build dir (preferable via the bblayers.conf). I think this should be
> possible because at the start of a build the revs are displayed like:
> meta-yocto = "[branch]:[commit-id]" The problem is that I wasn't able to
> find any answers or solutions on the web so I ask you now for help.

The build system doesn't actually manage checking out/updating layers for you, 
it only reports the revision if there is one, so this functionality isn't 
supported. Probably the easiest way to handle this would be to keep two 
separate checkouts.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: SRCREV for BBLAYERS

[Richard Leitner - SKIDATA]

Hi Paul,
thanks for your quick answer!
I'll work with separate checkouts for now...

But now I've got another question:
Is there any possibility to submit something like a feature request for this?
And is there a (realistic) chance that this feature gets implemented?
If so, where should this request go? To the bitbake-devel list?

best regards,
Richard

> -----Original Message-----
> From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
> Sent: Monday, February 03, 2014 3:46 PM
> To: Richard Leitner - SKIDATA
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] SRCREV for BBLAYERS
> 
> Hi Richard,
> 
> On Monday 03 February 2014 12:17:04 Richard Leitner - SKIDATA wrote:
> > I've a question regarding the BBLAYERS variable.
> > Is it possible to set some kind of a SRCREV (=> git
> > tag/branch/commit-id) for a path listed in BBLAYERS?
> >
> > I came to this question because I've two different branches in my meta
> > layer: one for development and one for 'stable' releases. Therefore I
> > have also two different build dirs and want to 'pin' the branches/tags
> > to the build dir (preferable via the bblayers.conf). I think this
> > should be possible because at the start of a build the revs are displayed like:
> > meta-yocto = "[branch]:[commit-id]" The problem is that I wasn't able
> > to find any answers or solutions on the web so I ask you now for help.
> 
> The build system doesn't actually manage checking out/updating layers for you, it only
> reports the revision if there is one, so this functionality isn't supported. Probably the
> easiest way to handle this would be to keep two separate checkouts.
> 
> Cheers,
> Paul
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre

Re: SRCREV for BBLAYERS

[Christian Ege]

Hi,

> Hi Paul,
> thanks for your quick answer!
> I'll work with separate checkouts for now...
>
> But now I've got another question:
> Is there any possibility to submit something like a feature request for this?
> And is there a (realistic) chance that this feature gets implemented?
> If so, where should this request go? To the bitbake-devel list?
I am not sure If I got your point. If you intend to handle different
versions of layers you are using you may can use the setup-scripts
from Angstrom
They do use an "layer manager"
https://github.com/Angstrom-distribution/setup-scripts
https://github.com/Angstrom-distribution/setup-scripts/blob/master/sources/layers.txt

Which fetches the configured layers with the defined branch and commit ID.


regards,
Christian

>
> best regards,
> Richard
>
>> -----Original Message-----
>> From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
>> Sent: Monday, February 03, 2014 3:46 PM
>> To: Richard Leitner - SKIDATA
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] SRCREV for BBLAYERS
>>
>> Hi Richard,
>>
>> On Monday 03 February 2014 12:17:04 Richard Leitner - SKIDATA wrote:
>> > I've a question regarding the BBLAYERS variable.
>> > Is it possible to set some kind of a SRCREV (=> git
>> > tag/branch/commit-id) for a path listed in BBLAYERS?
>> >
>> > I came to this question because I've two different branches in my meta
>> > layer: one for development and one for 'stable' releases. Therefore I
>> > have also two different build dirs and want to 'pin' the branches/tags
>> > to the build dir (preferable via the bblayers.conf). I think this
>> > should be possible because at the start of a build the revs are displayed like:
>> > meta-yocto = "[branch]:[commit-id]" The problem is that I wasn't able
>> > to find any answers or solutions on the web so I ask you now for help.
>>
>> The build system doesn't actually manage checking out/updating layers for you, it only
>> reports the revision if there is one, so this functionality isn't supported. Probably the
>> easiest way to handle this would be to keep two separate checkouts.
>>
>> Cheers,
>> Paul
>>
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: SRCREV for BBLAYERS

[Trevor Woerner]

On 02/03/14 10:20, Christian Ege wrote:
>> But now I've got another question:
>> Is there any possibility to submit something like a feature request for this?
>> And is there a (realistic) chance that this feature gets implemented?
>> If so, where should this request go? To the bitbake-devel list?
> I am not sure If I got your point. If you intend to handle different
> versions of layers you are using you may can use the setup-scripts
> from Angstrom
> They do use an "layer manager"

Some projects which use git face this "how to manage sets of git
repositories" issue[1]. Unless a project's sources are all contained in
one monster git repository, there will always be some sort of need for
management. The understanding is that not every single commit point in
every repository will work with every other commit point in all the
other repositories making up a project. There will be "way-points" where
things work and/or are tested, and all other combinations are to be used
at one's own risk ;-)

As pointed out above, angstrom has its own system. Other projects (e.g.
gumstix[2] and fsl[3]) make use of "repo". Another option is "git
submodules".

Whether a mechanism like this would be, could be, or should be added to
OE? That's a tough one. Personally I would lean towards "yes". I think
it would make OE much easier to use (especially for newcomers) if the
combinations of layers and which commits to use from those layers were
specified as part of a, say, DISTRO's metadata. On the other hand others
would object simply because this is a not-uncommon git issue that is
already solved by existing, external tools.

Best regards,
    Trevor


[1] http://stackoverflow.com/questions/816619/managing-many-git-repositories
[2]
https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/master/README.md
[3] https://github.com/Freescale/fsl-community-bsp-platform

Re: SRCREV for BBLAYERS

[Khem Raj]

> As pointed out above, angstrom has its own system. Other projects (e.g.
> gumstix[2] and fsl[3]) make use of "repo". Another option is "git
> submodules".
>
> Whether a mechanism like this would be, could be, or should be added to
> OE? That's a tough one. Personally I would lean towards "yes".

There already is a tool called combo-layer to create unified view by
combining layers
in OE-Core but its not one of above

 I think
> it would make OE much easier to use (especially for newcomers) if the
> combinations of layers and which commits to use from those layers were
> specified as part of a, say, DISTRO's metadata. On the other hand others
> would object simply because this is a not-uncommon git issue that is
> already solved by existing, external tools.

Re: SRCREV for BBLAYERS

[Trevor Woerner]

On 02/03/14 12:41, Khem Raj wrote:
> There already is a tool called combo-layer to create unified view by
> combining layers in OE-Core but its not one of above I think

Awesome! I hadn't noticed that before, thanks for pointing it out.