Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/download/git: Prioritize remote archive
Date: Mon, 22 Aug 2016 21:53:41 +0200	[thread overview]
Message-ID: <87zio4pol6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160817210314.GG5778@free.fr> (Yann E. MORIN's message of "Wed,  17 Aug 2016 23:03:14 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

 > 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

Or alternatively, we look at the alternative approach for handling
submodules - E.G. splicing git archive outputs.

 > 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.

Normal 'git archive' output should be reproducable, E.G. that is what we
used until recently.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2016-08-22 19:53 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
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 [this message]
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=87zio4pol6.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