<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 26, 2015 at 9:38 AM, Christopher Larson <span dir="ltr"><<a href="mailto:kergoth@gmail.com" target="_blank">kergoth@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":1l1" class="" style="overflow:hidden">From: Christopher Larson <<a href="mailto:chris_larson@mentor.com">chris_larson@mentor.com</a>><br>
<br>
Supercedes `[RFC PATCH 0/5] Implement git shallow mirror tarball support`.<br>
<br>
The shallow mirror tarball filename includes branch, revision, and depth. To<br>
enable, use the BB_GIT_SHALLOW variable, or BB_GIT_SHALLOW_<name> for specific<br>
URLs. This variable can hold either a clone depth (e.g. 1 to just get SRCREV),<br>
or a ref or commit, in which case we keep history up to that commit.<br>
<br>
Example:<br>
<br>
BB_GIT_SHALLOW ?= "1"<br>
BB_GIT_SHALLOW_pn-linux-yocto = ""<br>
BB_GIT_SHALLOW_pn-linux-mel_mx6 = "v3.14"<br>
BB_GIT_SHALLOW_pn-testrepo = "testbranch"<br>
<br>
Example in a recipe with multiple named uris, or multiple named branches in a<br>
single git URI:<br>
<br>
BB_GIT_SHALLOW_main = "1"<br>
BB_GIT_SHALLOW_doc = ""<br>
<br>
BB_GIT_SHALLOW affects both the tarballs being fetched and the mirror tarball<br>
which is created when BB_GENERATE_MIRROR_TARBALLS is enabled. If the shallow<br>
mirror tarball cannot be fetched, it will try to fetch the full mirror tarball<br>
and use that.<br>
<br>
Limitations:<br>
<br>
The shallow support will not, at this time, function correctly for<br>
linux-yocto, due to its branching scheme & validation.<br>
<br>
This implements support for shallow mirror tarballs, not shallow clones.<br>
Supporting shallow clones directly would be rather more problematic, as we'd<br>
need to hardcode the depth between branch HEAD and the SRCREV, and that depth<br>
would change as the branch is updated.</div></blockquote></div><br>One point of clarification, as it was asked with the RFC version of this series. This is in a comment, but I forgot to add it in the commit message:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><span style="font-size:13px">A current clone is preferred to either tarball, a shallow tarball is </span><span style="font-size:13px">preferred to an out of date clone, and a missing clone will use </span><span style="font-size:13px">either tarball.<br></span>-- <br><div class="gmail_signature"><div dir="ltr">Christopher Larson<br>kergoth at gmail dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div></div>
</div></div>