From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: bzr.eclass into Portage
Date: Wed, 15 Oct 2008 10:36:20 +0100 [thread overview]
Message-ID: <gd4e8k$6i2$2@ger.gmane.org> (raw)
In-Reply-To: 200810131723.17710.bo.andresen@zlin.dk
Bo Ørsted Andresen wrote:
> On Monday 13 October 2008 04:43:48 Steve Long wrote:
>> EBZR_OPTIONS="${EBZR_OPTIONS:-}" (and similar variants)
>> doesn't do anything (beyond waste lex and yacc time.)
>
> It gets listed in the generated man page.
>
From what I remember of the awk that generates those manpages, this:
# @ECLASS-VARIABLE: EBZR_OPTIONS
# @DESCRIPTION:
# The options passed to the fetch and update commands.
..does that.
>> The same consideration applies to all those "constant values" 'and
>> indeed' ${foo} as opposed to $foo, though first time I raised that I got
>> sworn at, so not expecting miracles here.
>
> Are you for real?
>
Perhaps you missed the discussion about EAPI in filenames?
next prev parent reply other threads:[~2008-10-15 9:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 18:31 [gentoo-dev] bzr.eclass into Portage Christian Faulhammer
2008-03-18 0:37 ` Petteri Räty
2008-03-19 4:40 ` Jorge Manuel B. S. Vicetto
2008-03-20 7:38 ` [gentoo-dev] " Christian Faulhammer
2008-03-21 3:47 ` Jorge Manuel B. S. Vicetto
2008-03-21 11:49 ` Christian Faulhammer
2008-03-25 1:28 ` René 'Necoro' Neumann
2008-03-25 15:19 ` René 'Necoro' Neumann
2008-03-25 20:08 ` Christian Faulhammer
2008-10-05 17:26 ` Ulrich Mueller
2008-10-05 20:54 ` Jonas Bernoulli
2008-10-06 0:58 ` Jorge Manuel B. S. Vicetto
2008-10-06 6:14 ` Ulrich Mueller
2008-10-13 2:43 ` Steve Long
2008-10-13 6:29 ` Ulrich Mueller
2008-10-13 15:23 ` Bo Ørsted Andresen
2008-10-15 9:36 ` Steve Long [this message]
2008-10-25 12:19 ` Ulrich Mueller
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='gd4e8k$6i2$2@ger.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