Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/9 v3] Cleanups in download helpers (branch yem/check-downloads)
Date: Sun, 27 Jul 2014 16:13:09 +0200	[thread overview]
Message-ID: <20140727161309.5ed9ad32@free-electrons.com> (raw)
In-Reply-To: <cover.1405895896.git.yann.morin.1998@free.fr>

Hello,

On Mon, 21 Jul 2014 00:42:22 +0200, Yann E. MORIN wrote:

> This series is a follow-up to the previous download series. Following
> the advice from Arnout, I introduced a wrapper script that is responsible
> for the saving atomically in BR2_DL_DIR. If also manages all the temporary
> files, and properly cleans up.
> 
> Consequently, the helpers are now nuch more simple, and no longer need to
> duplicate the complex handling of atomicity in BR2_DL_DIR, nor do they
> need to manage temporary files.

In principle, it certainly looks good. I'm just wondering if we really
need the separate scripts for each of the download methods, since they
do just one command basically. What about a single
support/scripts/download-helper script, which does the common stuff +
contains a switch to call the appropriate sub-functions for each
download method?

What do others think? Could some others test the patch series and give
their feedback?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-07-27 14:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20 22:42 [Buildroot] [PATCH 0/9 v3] Cleanups in download helpers (branch yem/check-downloads) Yann E. MORIN
2014-07-20 22:42 ` [Buildroot] [PATCH 1/9 v3] support/download: add download wrapper Yann E. MORIN
2014-08-03  7:18   ` Thomas De Schampheleire
2014-08-03  7:27     ` Yann E. MORIN
2014-07-20 22:42 ` [Buildroot] [PATCH 2/9 v3] support/download: convert bzr to use the wrapper Yann E. MORIN
2014-08-03  7:52   ` Thomas De Schampheleire
2014-08-03 17:05     ` Yann E. MORIN
2014-07-20 22:42 ` [Buildroot] [PATCH 3/9 v3] support/download: convert localfiles " Yann E. MORIN
2014-08-03  7:56   ` Thomas De Schampheleire
2014-08-03 17:06     ` Yann E. MORIN
2014-08-03 17:39   ` Thomas De Schampheleire
2014-07-20 22:42 ` [Buildroot] [PATCH 4/9 v3] support/download: convert cvs " Yann E. MORIN
2014-08-03 17:40   ` Thomas De Schampheleire
2014-07-20 22:42 ` [Buildroot] [PATCH 5/9 v3] support/download: convert git " Yann E. MORIN
2014-08-03 17:41   ` Thomas De Schampheleire
2014-07-20 22:42 ` [Buildroot] [PATCH 6/9 v3] support/download: convert Hg " Yann E. MORIN
2014-08-03 17:41   ` Thomas De Schampheleire
2014-07-20 22:42 ` [Buildroot] [PATCH 7/9 v3] support/download: convert scp " Yann E. MORIN
2014-08-03 17:42   ` Thomas De Schampheleire
2014-07-20 22:42 ` [Buildroot] [PATCH 8/9 v3] support/download: convert svn " Yann E. MORIN
2014-08-03 17:42   ` Thomas De Schampheleire
2014-07-20 22:42 ` [Buildroot] [PATCH 9/9 v3] support/download: convert wget " Yann E. MORIN
2014-08-03 17:43   ` Thomas De Schampheleire
2014-07-27 14:13 ` Thomas Petazzoni [this message]
2014-07-27 19:58   ` [Buildroot] [PATCH 0/9 v3] Cleanups in download helpers (branch yem/check-downloads) 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=20140727161309.5ed9ad32@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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