Excerpts from Aaron Griffin's message of Sun May 18 23:43:42 +0200 2008:
> > that would be totally illogical. the point of using ${foo} instead of
> > $foo is that in some cases you really need ${foo}:
> >
> > source=($pkgname_$pkgver) won't work, but source=(${pkgname}_$pkgver)
> > will. (just an example but probably you got the point). because of this,
> > some projects (like gentoo) force the usage of ${foo} everywhere.
>
> OT: I also enforce it in mkinitcpio scripts. It's not a bad idea, just
> more typing.
I think it's useless. We could also forget about PATH and always use
/usr/bin/find... We could also ALWAYS use quotes.
Now, should we replace:
find . -type f
by:
"/usr/bin/find" "." "-type" "f"
or make light and readable scripts, using the ${} form when necessary?
I think those questions are about do fair things and not make any extreme
choice. That's what I think pragmatism is, and what I love in Archlinux.
Anyway, it's not my call.
--
Geoffroy Carrier
http://gcarrier.koon.fr/
arch
Description: Binary data
_______________________________________________ pacman-dev mailing list pacman-dev@archlinux.org http://archlinux.org/mailman/listinfo/pacman-dev
