[bitbake-devel] [PATCH 0/7] Add symlinks for git (shallow) tarballs when name differs due to mirror rewrite rules

[Urs Fässler]

The git (shallow) tarballs are not found when certain mirror rewrite rules are
in use. This is due to the fact that the tarball is named according to the url
where it is downloaded from. The error occurs in the unpack step where BitBake
looks for a tarball named after the url as specified in the recipe. By adding
the symlinks BitBake finds the tarballs in the unpack step.

This is an alternative to the patches "Always use the url specified in the
recipe as a base for the git shallow tarball naming" from the 23.07.2018. This
solution is more aligned to the current implementation of BitBake.

Regards
Urs

Urs Fässler (7):
  fetch2/git: add tests to capture existing behavior wrt. naming of
    clone directories
  fetch2/git: add tests to capture existing behavior wrt. naming of
    mirror tarball
  fetch2/git: add tests to capture existing behavior wrt. naming of git
    shallow tarball
  fetch2/git: use intention revealing names for premirror tests
  fetch2: extract the function which ensures that a valid symlink exists
  fetch2: add symlinks for mirror tarballs
  fetch2: add symlink for shallow mirror tarballs

 lib/bb/fetch2/__init__.py |  31 +++--
 lib/bb/tests/fetch.py     | 235 ++++++++++++++++++++++++++++++++++++--
 2 files changed, 246 insertions(+), 20 deletions(-)

-- 
2.19.1