>>>>> On Sun, 21 Sep 2008, Steve Long wrote:
> Vaeth wrote:
>> let me remark that the more clever way to this is
>> [ -n "${DOCS}" ] && eval "dodoc ${DOCS}"
> [...]
> BASH arrays will cope with *any* character apart from NUL, which
> isn't allowed in filenames. Can you _guarantee_ the same?
It seems to me that both bash arrays and "eval" are overkill here.
After all, we are talking about a _default_ behaviour, and IMHO this
should be kept as simple as possible. I doubt that there are many
ebuilds installing files with strange names in /usr/share/doc. The few
(if any) doing that might need a more complicated src_install anyway.
My system may not be representative, but here are _no_ files
containing spaces in /usr/share/doc:
$ find /usr/share/doc | wc
104936 104936 7522127
(Note that the number of lines and words are equal.)
Ulrich
