1 |
On Mon, Sep 22, 2008 at 1:04 AM, Ulrich Mueller <ulm@g.o> wrote: |
2 |
> |
3 |
> >>>>> On Sun, 21 Sep 2008, Steve Long wrote: |
4 |
> |
5 |
> > Vaeth wrote: |
6 |
> >> let me remark that the more clever way to this is |
7 |
> >> [ -n "${DOCS}" ] && eval "dodoc ${DOCS}" |
8 |
> |
9 |
> > [...] |
10 |
> > BASH arrays will cope with *any* character apart from NUL, which |
11 |
> > isn't allowed in filenames. Can you _guarantee_ the same? |
12 |
> |
13 |
> It seems to me that both bash arrays and "eval" are overkill here. |
14 |
> |
15 |
> After all, we are talking about a _default_ behaviour, and IMHO this |
16 |
> should be kept as simple as possible. I doubt that there are many |
17 |
> ebuilds installing files with strange names in /usr/share/doc. The few |
18 |
> (if any) doing that might need a more complicated src_install anyway. |
19 |
> |
20 |
> My system may not be representative, but here are _no_ files |
21 |
> containing spaces in /usr/share/doc: |
22 |
> |
23 |
> $ find /usr/share/doc | wc |
24 |
> 104936 104936 7522127 |
25 |
> |
26 |
> (Note that the number of lines and words are equal.) |
27 |
> |
28 |
> Ulrich |
29 |
> |
30 |
|
31 |
find /usr/share/doc/ -wholename "* *" |
32 |
/usr/share/doc/gpac-0.4.4-r1/ISO 639-2 codes.txt.bz2 |
33 |
|
34 |
And in case somebody gets space-phobic on a different directory : |
35 |
|
36 |
find /usr/ -wholename "* *" |
37 |
/usr/kde/4.2/share/applnk/Development/Web Development |
38 |
/usr/kde/svn/share/applnk/Development/Web Development |
39 |
/usr/share/applnk/Development/Web Development |
40 |
/usr/share/doc/gpac-0.4.4-r1/ISO 639-2 codes.txt.bz2 |
41 |
/usr/share/lcms/profiles/sRGB Color Space Profile.icm |
42 |
/usr/share/mixxx/( Lots here ) |
43 |
|
44 |
|
45 |
¢¢ ( Apps that break on spaces are embarrasing ) |
46 |
-- |
47 |
Kent |
48 |
|
49 |
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x| |
50 |
print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}' |
51 |
|
52 |
http://kent-fredric.fox.geek.nz |