public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: [RFC] base.eclass
Date: Sun, 3 Jan 2010 12:00:37 +0100	[thread overview]
Message-ID: <20100103110037.GA29047@boostbox> (raw)
In-Reply-To: <19264.29027.852829.477540@a1i15.kph.uni-mainz.de>

On Sun, Jan 03, 2010 at 11:28:27AM +0100, Ulrich Mueller wrote:
> >>>>> On Sun, 3 Jan 2010, Harald van Dijk wrote:
> 
> >> > 65                 base_src_util $@
> >> This is not problem
> 
> > Only because you can be sure there will be exactly one word in the
> > result, which will not be split. In general, $@ should be quoted, and it
> > would be a good idea to either do it here too even though it's not
> > strictly necessary, or make the intent clearer and just write
> 
> >   base_src_util $1
> 
> I think this would not be correct. Note the while loop over parameters
> in base_src_util.

You're right. I'm so used to src_unpack normally not having any arguments
that I didn't stop to think base_src_unpack could easily be called
explicitly, with as many parameters as you'd like. Checking shows this
is not done in the tree (never more than one parameter, and usually
zero), but that's no reason to drop it. :)

> So it should be "$@" (with quotes).

That'd be better, but my point still stands: the arguments to
base_src_unpack won't ever contain anything that can be expanded, so quoting
isn't strictly necessary, just a good idea.

Not that I'm against the quoting, of course.



      reply	other threads:[~2010-01-03 11:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02 15:52 [gentoo-dev] [RFC] base.eclass Tomáš Chvátal
2010-01-02 16:12 ` Ben de Groot
2010-01-02 16:31   ` Tomáš Chvátal
2010-01-03  0:56 ` [gentoo-dev] " Mark Bateman
2010-01-03  1:56   ` Tomáš Chvátal
2010-01-03  6:23     ` Harald van Dijk
2010-01-03 10:28       ` Ulrich Mueller
2010-01-03 11:00         ` Harald van Dijk [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=20100103110037.GA29047@boostbox \
    --to=truedfx@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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