From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/6] support/download: Add support to pass options directly to downloaders
Date: Sun, 24 Jul 2016 16:00:48 +0200 [thread overview]
Message-ID: <20160724160048.39770315@free-electrons.com> (raw)
In-Reply-To: <20160715204729.GH3692@free.fr>
Hello,
On Fri, 15 Jul 2016 22:47:29 +0200, Yann E. MORIN wrote:
> > ---
> [--SNIP--]
> > diff --git a/support/download/bzr b/support/download/bzr
> > index e18b01f..9443e03 100755
> > --- a/support/download/bzr
> > +++ b/support/download/bzr
> > @@ -25,6 +25,7 @@ output="${1}"
> > repo="${2}"
> > rev="${3}"
> > basename="${4}"
> > +dl_opts="${5}"
>
> So we expect the additional options to be pased as a single string?
> Why not use something like:
>
> shift 4 # Get rid of our options
>
> and then:
>
> _bzr export ${verbose} --root="'${basename}/'" --format=tgz \
> ${timestamp_opt} - "'${repo}'" -r "'${rev}'" \
> ${timestamp_opt} - "${@}" "'${repo}'" -r "'${rev}'" \
>
> Ditto for all backends, of course.
>
> Note: I wrote the above after writing the comment below; that construct
> above would fix the concerns I expressed below.
>
> (I'm hard to follow, am I not? My brain is really tortuous... ;-] )
Below, you're concerned that "${dl_opts}" will lead to a problem as it
will be an empty "" if no options are passed. But you suggest to use
"${@}" instead, still with "". How does that fix the particular problem
you mentioned below?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-24 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 9:30 [Buildroot] [PATCH v2 0/6] Add support for AMD Catalyst graphics driver Romain Perier
2016-07-12 9:30 ` [Buildroot] [PATCH v2 1/6] support/download: Add support to pass options directly to downloaders Romain Perier
2016-07-15 15:54 ` Yann E. MORIN
2016-07-15 17:21 ` Thomas Petazzoni
2016-07-15 20:47 ` Yann E. MORIN
2016-07-24 14:00 ` Thomas Petazzoni [this message]
2016-07-24 14:04 ` Yann E. MORIN
2016-07-24 14:05 ` Thomas Petazzoni
2016-07-26 7:31 ` Romain Perier
2016-07-12 9:30 ` [Buildroot] [PATCH v2 2/6] pkg-download: Allow packages to pass generic options to download methods Romain Perier
2016-07-15 15:56 ` Yann E. MORIN
2016-07-12 9:30 ` [Buildroot] [PATCH v2 3/6] docs/manual: Document the variable $(PKG)_DL_OPTS Romain Perier
2016-07-15 16:00 ` Yann E. MORIN
2016-07-26 7:30 ` Romain Perier
2016-07-12 9:30 ` [Buildroot] [PATCH v2 4/6] package/xserver_xorg-server: add version 1.17.4 Romain Perier
2016-07-15 13:23 ` Thomas Petazzoni
2016-07-12 9:30 ` [Buildroot] [PATCH v2 5/6] qt: Add option for enabling the accessibility support Romain Perier
2016-07-15 13:23 ` Thomas Petazzoni
2016-07-12 9:30 ` [Buildroot] [PATCH v2 6/6] package/amd-catalyst-driver: Add AMD proprietary graphic stack support Romain Perier
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=20160724160048.39770315@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