From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Revbumped php-ext-* eclasses
Date: Sat, 09 Oct 2010 20:19:45 +0400 [thread overview]
Message-ID: <1286641185.3611.550.camel@tablet> (raw)
In-Reply-To: <4CA86BE8.5030707@gentoo.org>
Hi!
В Вск, 03/10/2010 в 13:41 +0200, Ole Markus With пишет:
> for slot in `php_get_slots`; do
It's better use $() instead of backticks:
http://mywiki.wooledge.org/BashFAQ/082
> [[ -z "${PHP_EXT_ZENDEXT}" ]] && PHP_EXT_ZENDEXT="no"
>
...
> [[ -z "$USE_PHP" ]] && USE_PHP="php5-2 php5-3"
In some places eclass uses ${var} syntax but here and later it uses
$var. I'm not sure which syntax is better but in Gentoo we use ${var}
and for readability it's better to stick to single style.
> php_get_slots() {
> local s
> local slot
single $(local s slot) is enough here.
> php_init_slot_env() {
...
> S="${WORKDIR}/$1"
> cd $S
S is unquoted, and ${}
> php-ext-source-r2_buildinilist() {
...
> for x in ${PHPSAPILIST} ; do
local x?
--
Peter.
prev parent reply other threads:[~2010-10-09 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 11:41 [gentoo-dev] Revbumped php-ext-* eclasses Ole Markus With
2010-10-06 18:06 ` Donnie Berkholz
2010-10-06 19:36 ` Ole Markus With
2010-10-09 16:19 ` Peter Volkov [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=1286641185.3611.550.camel@tablet \
--to=pva@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