[bitbake-devel] [PATCH] fetch2: try PREMIRRORS when calculating latest_revision

Enrico Scholz enrico.scholz at sigma-chemnitz.de
Wed Jul 4 16:57:35 UTC 2012


Richard Purdie <richard.purdie at linuxfoundation.org> writes:

>> Since support for native git mirrors was added in recent bitbake, it
>> is possible to use local mirrors for calculating ${AUTOREV}.
>
> I'm torn over this one. If you want to refer to local changes wouldn't
> it make more sense just to totally override SRC_URI in cases

Modifying SRC_URI is a pain (split it into components, find the matching
one and replace it with the new one; managing the .bbappend file with
this code).  A declarative syntax like for PREMIRRORS is much easier too
handle and maintain.

Before native git mirrors were supported I solved it by 'url.<new>.insteadOf'
config option. But, this requires either a very recent git to set the '-c'
option in FETCHCMD_git, or the modification of global ~/.gitconfig (which
will cause conflicts and bad surprises when having multiple projects).


> I'm worried that here, upstream revisions may just get ignored for
> example with just a premirror copy being consulted and this wouldn't
> be the expected behaviour a user would want.

That's already the case with recent PREMIRRORs.  People will get the
version which is in PREMIRROR, not the upstream one.

Difference is that after applying my patch, the early recipe-parsing
will not fail when upstream unavailable.


Enrico




More information about the bitbake-devel mailing list