| 1 |
On Wednesday 14 November 2007, Ferris McCormick wrote: |
| 2 |
> Note, however, that for example in /usr/lib/portage/bin/ebuild.sh, it's |
| 3 |
> always quoted (except once, which looks like an oversight). |
| 4 |
|
| 5 |
I was talking about referencing variables when declaring other variables. |
| 6 |
Whenever you actually use a variable in-line (e.g. as a parameter to a |
| 7 |
command), you have to quote as well of course. |
| 8 |
i.e. |
| 9 |
A=${B} |
| 10 |
and not |
| 11 |
cd ${B} |
| 12 |
|
| 13 |
The difference is that bash handles variable assignments all interally and is |
| 14 |
smart enough to handle ${B} properly, while vars that are passed to some |
| 15 |
command are just evaluated and passed to the command in question and cannot |
| 16 |
be "protected" anymore by bash. AFAIK. |
| 17 |
|
| 18 |
-- |
| 19 |
Torsten Rehn <scel@××××.org> |
| 20 |
Gentoo AMD64 Arch Tester |
| 21 |
http://scel.info |
Archives