From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: Re: [gentoo-commits] gentoo-x86 commit in x11-libs/qt: ChangeLog qt-4.3.2.ebuild
Date: Fri, 5 Oct 2007 17:06:18 -0700 [thread overview]
Message-ID: <20071006000618.GP29572@supernova> (raw)
In-Reply-To: <fe6hrs$hej$1@sea.gmane.org>
On 00:41 Sat 06 Oct , Steve Long wrote:
> Donnie Berkholz wrote:
> > On 13:34 Fri 05 Oct , Steve Long wrote:
> >> In actual fact, I'd be more likely to use parameter expansion than set,
> >> eg: spec=${CHOST#*-*-} # chop first two fields off so spec is fields 3 on
> >> spec=${spec%%-*} # chop all but first off so left with just field 3
> >> ..which I believe works in sh[1] as well. The point for me, however, is
> >> not whether sh can be kludged to do something, it's what the most
> >> efficient ways to do something in scripts are. Whether you use pe, read
> >> or an array, avoiding externals leads to quicker scripts.[2]
> >
> > That parameter workaround wouldn't work, because CHOST may also contain
> > just 3 fields, as it does on Gentoo/BSD. Unpack a portage tarball and
> > look at the make.conf's if you're curious.
> >
> Then the second expansion would have no effect.
Good point.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-10-06 0:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Id5gB-0006KU-HS@stork.gentoo.org>
2007-10-03 17:38 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-libs/qt: ChangeLog qt-4.3.2.ebuild Donnie Berkholz
2007-10-03 18:05 ` Caleb Tennis
2007-10-04 4:03 ` Steve Long
2007-10-04 6:49 ` Roy Marples
2007-10-04 7:32 ` Donnie Berkholz
2007-10-04 7:43 ` Roy Marples
2007-10-04 9:53 ` Marijn Schouten (hkBst)
2007-10-04 10:11 ` Roy Marples
2007-10-05 12:34 ` [gentoo-dev] " Steve Long
2007-10-05 17:50 ` Donnie Berkholz
2007-10-05 23:41 ` [gentoo-dev] " Steve Long
2007-10-06 0:06 ` Donnie Berkholz [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=20071006000618.GP29572@supernova \
--to=dberkholz@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