[bitbake-devel] [PATCH] BB_NO_NETWORK: Fallback to local source for git lsremote

[Khem Raj]

> On Aug 9, 2016, at 2:36 AM, Olof Johansson <olof.johansson at axis.com> wrote:
> 
> On 16-08-08 10:22 -0700, Khem Raj wrote:
>> you are confusing how a tool is specifying its functions with
>> process that could emulate a different behavior. OE does not
>> have any control over the internal processes of its users and
>> it should not have.
> 
> No, I don't think I'm confusing anything. Are you confusing OE
> and bitbake? We maintain and develop an in-house Poky based
> distribution, and unlike OE, we know a lot about our
> users/developers.

its a typo.
Thats fine. You can maintain this change locally for your use case.

> 
>>> Tags are only a problem in git if people insist on
>>> modifying/deleting them.
>> 
>> Fact is, its allowed rewrite tags in git, how people use it or not
>> is irrelevant here.
> 
> Nope, Git is a protocol; git the tool can't do nothing about a

Too literal, I guess a reader is getting what I was referring to

> server refusing to (re)move a tag. Your view of what a git tags
> is yours. Tags are meant to be static, otherwise they wouldn't
> have been synced to all clones in such a silly namespace.
> 
> While I agreed with Tobias' patch ("if you use tags in your
> builds, and use BB_NO_NETWORK, you are ok with falling back to
> what you have locally"), RP had a point about this making
> BB_NO_NETWORK have non-obvious side-effects, and also making it
> harder to catch cases where tags aren't wanted (like in community
> maintained layers).
> 
> But *we* still want to use human readable tags as the only
> version string internally (for our layers), where we know we are
> in control. So, introducing a variable that lets us opt-in to
> this behavior sounds like something that could be accepted?

If you were to think of a tool to generate the srcrevs from tags, that IMO
can be better solution here. Like Paul suggested.
-------------- 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/bitbake-devel/attachments/20160809/ea56feee/attachment-0002.sig>