From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/download/git: Prioritize remote archive
Date: Wed, 17 Aug 2016 23:03:14 +0200 [thread overview]
Message-ID: <20160817210314.GG5778@free.fr> (raw)
In-Reply-To: <1471461016-9660-1-git-send-email-kamath.ben@gmail.com>
Benjamin, All,
On 2016-08-17 12:10 -0700, Benjamin Kamath spake thusly:
> Attempt to do a remote archive since it shortcuts us past a few steps when
> available. Additionally. if the git server has uploadArchive.allowUnreachable
> set to true, then this method can also work on arbitrary sha1s, offering a huge
> speed advantage over a full clone.
>
> Signed-off-by: Benjamin Kamath <kamath.ben@gmail.com>
> ---
> support/download/git | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/support/download/git b/support/download/git
> index 416cd1b..043a6de 100755
> --- a/support/download/git
> +++ b/support/download/git
> @@ -36,6 +36,15 @@ _git() {
> eval ${GIT} "${@}"
> }
>
> +# Try a remote archive, since it is as fast as a shallow clone and can give us
> +# an archive directly. Also, if uploadArchive.allowUnreachable is set to true
> +# on the remote, this will also work for arbitrary sha1s, and will offer a
> +# considerable speedup over a full clone.
> +printf "Doing remote archive\n"
> +if _git archive --format=tar.gz --prefix=${basename}/ --remote=${repo} -o ${output} ${cset} 2>&1; then
> + exit 0
> +fi
NAK in the state.
If the package needs submodules, we can't ask the remote to generate
the archive for us, because git-archive does not know how to include
submodules.
So, maybe this would work:
if [ ${recurse} -eq 0 ]; then
if _git blabla remote archive; then
exit 0
fi
fi
Also, as stated by Thomas, we want to generate reproducible archives, so
that we can check the hashes of archives. We go at great length to
generate such archives locally, but I don't see a guarantee that the
remote archive would be reproducible.
Regards,
Yann E. MORIN.
> # Try a shallow clone, since it is faster than a full clone - but that only
> # works if the version is a ref (tag or branch). Before trying to do a shallow
> # clone we check if ${cset} is in the list provided by git ls-remote. If not
> --
> 2.7.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-08-17 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 19:10 [Buildroot] [PATCH 1/1] support/download/git: Prioritize remote archive Benjamin Kamath
2016-08-17 20:39 ` Thomas Petazzoni
2016-08-17 21:06 ` Benjamin Kamath
2016-08-17 21:03 ` Yann E. MORIN [this message]
2016-08-17 21:13 ` Benjamin Kamath
2016-08-17 21:31 ` Yann E. MORIN
2016-08-17 21:54 ` Thomas Petazzoni
2016-08-17 22:00 ` Yann E. MORIN
2016-08-22 19:53 ` Peter Korsgaard
2016-08-22 20:55 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160817210314.GG5778@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox