2014-07-02 23:11:19 +02:00
|
|
|
#!/bin/bash
|
|
|
|
|
2014-08-03 19:53:38 +02:00
|
|
|
# We want to catch any unexpected failure, and exit immediately
|
2014-07-02 23:11:19 +02:00
|
|
|
set -e
|
|
|
|
|
2014-08-03 19:53:38 +02:00
|
|
|
# Download helper for git, to be called from the download wrapper script
|
|
|
|
# Expected arguments:
|
|
|
|
# $1: output file
|
|
|
|
# $2: git repo
|
|
|
|
# $3: git cset
|
|
|
|
# $4: package's basename (eg. foobar-1.2.3)
|
2014-07-02 23:11:19 +02:00
|
|
|
# And this environment:
|
pkg-infra: don't use DL_DIR as scratchpad for temporary downloads
DL_DIR can be a very precious place for some users: they use it to store
all the downloaded archives to share across all their Buildroot (and
maybe non-Buildroot) builds.
We do not want to trash this location with our temporary downloads (e.g.
git, Hg, svn, cvs repository clones/checkouts, or wget, bzr tep tarballs).
Turns out that we already have some kind of scratchpad, the BUILD_DIR.
Although it is not really a disposable location, that's the best we have
so far.
Also, we create the temporary tarballs with mktemp using the final tarball,
as template, since we want the temporary to be on the same filesystem as
the final location, so the 'mv' is just a plain, atomic rename(2), and we
are not left with a half-copied file as the final location.
Using mktemp ensures all temp file names are unique, so it allows for
parallel downloads from different build dirs at the same time, without
cloberring each downloads.
Note: we're using neither ${TMP} nor ${TMPDIR} since they are shared
locations, sometime with little place (eg. tmpfs), and some of the
repositories we clone/checkout can be very big.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Samuel Martin <s.martin49@gmail.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Tested-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
[tested a particular scenario that used to fail: two separate builds
using a shared DL_DIR, ccache enabled, so that they run almost
synchronously. These would download the same file at the same time,
corrupting each other. With the patches in this series, all works
fine.]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-07-03 21:36:20 +02:00
|
|
|
# GIT : the git command to call
|
2014-07-02 23:11:19 +02:00
|
|
|
|
2014-08-03 19:53:38 +02:00
|
|
|
output="${1}"
|
|
|
|
repo="${2}"
|
|
|
|
cset="${3}"
|
|
|
|
basename="${4}"
|
2014-07-02 23:11:19 +02:00
|
|
|
|
2014-08-03 19:53:38 +02:00
|
|
|
# Try to see if we can do a shallow clone, since it is faster
|
|
|
|
# than a full clone.
|
2014-07-02 23:11:19 +02:00
|
|
|
if [ -n "$(${GIT} ls-remote "${repo}" "${cset}" 2>&1)" ]; then
|
|
|
|
printf "Doing shallow clone\n"
|
2014-08-03 19:53:38 +02:00
|
|
|
if ${GIT} clone --depth 1 -b "${cset}" --bare "${repo}" "${basename}"; then
|
2014-07-07 23:44:33 +02:00
|
|
|
git_done=1
|
2014-08-03 19:53:38 +02:00
|
|
|
else
|
|
|
|
printf "Shallow clone failed, falling back to doing a full clone\n"
|
2014-07-07 23:44:33 +02:00
|
|
|
fi
|
|
|
|
fi
|
|
|
|
if [ ${git_done} -eq 0 ]; then
|
2014-07-02 23:11:19 +02:00
|
|
|
printf "Doing full clone\n"
|
2014-08-03 19:53:38 +02:00
|
|
|
${GIT} clone --bare "${repo}" "${basename}"
|
2014-07-02 23:11:19 +02:00
|
|
|
fi
|
|
|
|
|
2014-08-03 19:53:38 +02:00
|
|
|
GIT_DIR="${basename}" \
|
|
|
|
${GIT} archive --prefix="${basename}/" -o "${output}" --format=tar "${cset}"
|
2014-07-02 23:11:19 +02:00
|
|
|
|
2014-08-03 19:53:38 +02:00
|
|
|
gzip "${output}"
|