public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Re: Quoting patch for repoman
Date: Mon, 01 Oct 2007 15:12:58 +0100	[thread overview]
Message-ID: <fdqv2v$d5j$1@sea.gmane.org> (raw)
In-Reply-To: 200710010704.48114.vapier@gentoo.org

Mike Frysinger wrote:

> On Monday 01 October 2007, Steve Long wrote:
>> A place to start might be a list of all known variables from say the
>> devmanual, along with whether they're allowed to be used as
>> multi-parameters in `for' or function/cmd calls. So it's legitimate to
>> see eg: for f in $A (even if it isn't space-proofed; that'd need an
>> array.)
> 
> i dont see how this is relevant, plus i dont really understand what you're
> trying to say.  this "multi-parameters" business just doesnt make sense.

Relevance is wrt automated checks for quoting, ie having a list of
variables[1] like WORKDIR and T to check for quoting issues.

Multi-parameter: according to devmanual, A is:
"All the source files for the package (excluding those which are not
available because of USE flags)."
So it's a (presumably whitespace-separated) list of values, not just a
singleton. Sorry if "multi-parameters" was a bad choice of word.

[1] http://devmanual.gentoo.org/ebuild-writing/variables/index.html


-- 
gentoo-dev@gentoo.org mailing list



      reply	other threads:[~2007-10-01 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-29  8:09 [gentoo-dev] Quoting patch for repoman Donnie Berkholz
2007-09-29  8:33 ` Donnie Berkholz
2007-09-29  8:44   ` Donnie Berkholz
2007-09-29  8:52   ` Mike Frysinger
2007-09-29 20:10     ` Donnie Berkholz
2007-09-30 18:26       ` Zac Medico
2007-10-01  1:53         ` Mike Frysinger
2007-10-01  2:36           ` Alec Warner
2007-10-01 11:41             ` Alec Warner
2007-10-01 10:53           ` [gentoo-dev] " Steve Long
2007-10-01 11:04             ` Mike Frysinger
2007-10-01 14:12               ` Steve Long [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='fdqv2v$d5j$1@sea.gmane.org' \
    --to=slong@rathaus.eclipse.co.uk \
    --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