From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: bzr.eclass into Portage
Date: Mon, 13 Oct 2008 03:43:48 +0100 [thread overview]
Message-ID: <gcudaj$bo9$1@ger.gmane.org> (raw)
In-Reply-To: 18665.44245.631670.638507@a1ihome1.kph.uni-mainz.de
Ulrich Mueller wrote:
>>>>>> On Mon, 06 Oct 2008, Jorge Manuel B S Vicetto wrote:
>
>> No objections here, just a question. Do you know if the issue with the
>> lp:// sources has been fixed in bzr?
>
No objections, a minor point wrt bash:
EBZR_OPTIONS="${EBZR_OPTIONS:-}" (and similar variants)
doesn't do anything (beyond waste lex and yacc time.) I can understand the
maintenance argument, but I don't think it really flies, given the
inordinate lengths considered in the past to avoid sourcing an ebuild.
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.
[[ -z ${EBZR_REPO_URI} ]] && die ..
Here's how I'd write that:
[[ $EBZR_REPO_URI ]] || die ..
I've heard the "be explicit" argument before (hey antarus;) and here's why I
disagree:
If you don't know test (''help test'') and what its default is, then you
really don't know the basics of shellscript (you possibly only think you
do.) If you don't know shell, and can't begin to understand what that might
do, then you shouldn't consider coding as a career, and I'd expect you to
take quite a while to go through the #bash crucible; if you ever make it
I'd have a lot of time for you.
(Since you use || elsewhere, I don't expect to hear the "|| is cryptic even
if we say OR in speech" argument.)
I appreciate that appears like 3 or 4 points: they all come under the 'clean
bash' heading: it runs faster, as well as being easier to read and write.
> Looks like this is working fine with bzr-1.5, so I'll change the
> dependency.
>
Given that, is there any reason not to use 1.6 if installed, and fallback to
an earlier version if not? Personally I'd just use an unversioned dep in
the latter case, given that 1.5 is stable and 1.7.1 is ~arch (amd64).
Doesn't sound like it's going to be long to get 1.6.
I'm thinking: "maximise utility before you unleash it on the tree".
next prev parent reply other threads:[~2008-10-13 2:55 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 [this message]
2008-10-13 6:29 ` Ulrich Mueller
2008-10-13 15:23 ` Bo Ørsted Andresen
2008-10-15 9:36 ` [gentoo-dev] " Steve Long
2008-10-25 12:19 ` [gentoo-dev] " 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='gcudaj$bo9$1@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