All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/5] package: add generic support for lz archives
Date: Thu, 16 Feb 2017 23:03:56 +0100	[thread overview]
Message-ID: <87efyxg5df.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170216174124.GB4986@free.fr> (Yann E. MORIN's message of "Thu,  16 Feb 2017 18:41:24 +0100")

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

Hi,

 > Actually, there is a use-case for being able to specify some of those,
 > at least the downloaders: git, wget, svn, scp...

 > I use a script that is called in lieue of each downloader:

 >     BR2_WGET="/path/to/wrapper wget --passive-ftp -nd -t 3"
 >     BR2_GIT="/path/to/wrapper git"
 >     and so on...

 > That script is responsible for memorising, for each package, whether it
 > was downloaded from the primary mirror, the official site, or the backup
 > mirror, then acts according to where the package was downloaded:

 >   - from the primary mirror, nothing is done,

 >   - from the official site: it sends the archive to the primary mirror,
 >     and add it to a report,

 >   - from the backup site: it sends the archive to the primary mirror,
 >     and adds it to a report.

 > This is done by a Jenkins job, which gets both reports as the result. If
 > any of the reports is non-empty, the build is marked failed.

 > This allows us to:

 >   - automatically track new dependencies added by Joe Random Developer,
 >     especially transitive dependencies he might not be aware of,

 >   - automatically feed our local mirror so we are not dependent on
 >     upstream or s.b.o.

Nice, but presumably you could also simply create a directory with
wget/git/svn/.. symlinks to your wrapper and prepend that to your path
before running buildroot, and then change the wrapper to do its stuff
and call further in the path for the real tool, similar to the recently
added date wrapper for reproducable builds?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-02-16 22:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 20:15 [Buildroot] [PATCH v3 1/5] package: refactor listing of extractor dependencies Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 2/5] package: add generic support for lz archives Baruch Siach
2017-02-14 13:43   ` Thomas De Schampheleire
2017-02-15 21:15   ` Thomas Petazzoni
2017-02-15 22:48     ` Arnout Vandecappelle
2017-02-16  7:32       ` Thomas Petazzoni
2017-02-16  8:25         ` Arnout Vandecappelle
2017-02-16  8:34           ` Thomas Petazzoni
2017-02-16 17:24             ` Arnout Vandecappelle
2017-02-16 17:41       ` Yann E. MORIN
2017-02-16 22:03         ` Peter Korsgaard [this message]
2017-02-16 22:11           ` Yann E. MORIN
2017-02-17  7:43             ` Arnout Vandecappelle
2017-02-17 17:07               ` Yann E. MORIN
2017-02-16 22:08       ` Peter Korsgaard
2017-02-16  8:36     ` Thomas De Schampheleire
2017-02-16  8:40       ` Thomas Petazzoni
2017-02-16 10:24         ` Thomas De Schampheleire
2017-02-21 21:55   ` [Buildroot] Bug in "package: add generic support for lz archives" ? Thomas Petazzoni
2017-02-22  5:32     ` Baruch Siach
2017-02-22  8:03       ` Thomas Petazzoni
2017-02-12 20:15 ` [Buildroot] [PATCH v3 3/5] ed: use generic extract command Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 4/5] ddrescue: " Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 5/5] ocrad: " Baruch Siach
2017-02-14 13:42 ` [Buildroot] [PATCH v3 1/5] package: refactor listing of extractor dependencies Thomas De Schampheleire
2017-02-14 21:39 ` Thomas Petazzoni
2017-02-15  7:04   ` Baruch Siach
2017-02-15 21:13 ` Thomas Petazzoni

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=87efyxg5df.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.