From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/glibc: switch to downloading a tarball
Date: Tue, 14 Nov 2017 14:04:34 +0100 [thread overview]
Message-ID: <8760ad2eql.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171113213017.19371-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Mon, 13 Nov 2017 22:30:17 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Currently, we do a full git clone of the repository, which takes quite
> some time, especially on slow networks.
> This was done like that because the initial patch was using the official
> repository as the source of the download, and that repository did not
> offer remotely-generated tarballs.
> But now we've switched to using a mirror on github, which does provide
> such a tarball, which provides faster downloads.
> Use that.
> However, the tarball from github differs from the one we were generating
> locally, because the paths inside are different. WE used to create a
> archive with paths starting with glibc-glibc-2.26-73-g4b692dfb95[...],
> while github does away with the git-describe prefix, and generates paths
> that start with just glibc-4b692dffb95[...]. The content are exactly
> identicall (checked with a diff), though.
> Update the hash accordingly.
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Waldemar Brodkorb <wbx@openadk.org>
> Cc: Romain Naour <romain.naour@gmail.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-11-14 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 21:30 [Buildroot] [PATCH] package/glibc: switch to downloading a tarball Yann E. MORIN
2017-11-14 13:04 ` Peter Korsgaard [this message]
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=8760ad2eql.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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