[OE-core] should a "*git.bb" recipe lock that recipe to a fixed version?

[Khem Raj]

> On Oct 30, 2016, at 4:36 PM, Burton, Ross <ross.burton at intel.com> wrote:
> 
> 
> On 30 October 2016 at 17:35, Robert P. J. Day <rpjday at crashcourse.ca <mailto:rpjday at crashcourse.ca>> wrote:
>   fair enough ... i'm embarrassed to admit i didn't really understand
> the versioning selection so i'm going to examine it way more carefully
> now. i wonder how many recipes in oe-core are "_git" recipes that, in
> the end, just lock down to a specific version. as you say, i was a bit
> surprised.
> 
> Personally I've been endorsing the practise where _git.bb <http://git.bb/> is only used for recipes that are actually tracking git development branches, and if it's just a release that it simply fetched over git via a SHA of a release tag then the recipe should be _1.2.3.bb <http://1.2.3.bb/> for clarity.

with a system integrators hat on I agree. With developer hat on I do not.

> 
> Ross
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20161030/8dcdb3ee/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20161030/8dcdb3ee/attachment-0002.sig>