[bitbake-devel] [PATCH] fetch2/git: always use premirror first if update is required

Pascal Bach pascal.bach at siemens.com
Thu Sep 22 07:45:29 UTC 2016


>>     The tarball should only be fetched if the local ud.clonedir is out of date, this means the revision that is requested via SRCREV is not in the local repository.
>>     In the case the revision is present the tarball should not be fetched again, at least that was the intention and my local tests didn't indicate otherwise.
>>
>>
>> Yes, but it’s better to run ‘git fetch’ in an out of date clone than to re-download a 1gb mirror tarball which may well be out of date too.
> Agreed, but this doesn't work in the case where the machine doesn't have access to the upstream git repository. For example in the case where BB_ALLOWED_NETWORKS = "*.my.company". The fetcher would still got to to github.com which is not allowed, in that case it should fall back to fetch the tarball from "mirror.my.company".
>
> I'm open for suggestions how to make this more efficient.
Does anyone have a suggestion how this should behave in the ideal case? In my opinion if there is an internal mirror defined it should always have precedence even if it might be less efficient.

Pascal




More information about the bitbake-devel mailing list