1 |
On Fri, 09 Feb 2007 01:03:04 -0800 |
2 |
Donnie Berkholz <dberkholz@g.o> wrote: |
3 |
|
4 |
> Jakub Moc wrote: |
5 |
> > Mike Frysinger napsal(a): |
6 |
> >> On Thursday 08 February 2007, Roy Marples wrote: |
7 |
> >>> The actual scripts themselves can be re-worked if they need to be |
8 |
> >>> - this problem only when the arrays are used in config files. |
9 |
> >> i guess my point was i think we really need to be consistent |
10 |
> >> here ... either arrays are OK for init.d scripts or they're not OK |
11 |
> >> |
12 |
> >> did you get a chance to see how hard it would be to integrate the |
13 |
> >> bash array code ? |
14 |
> > |
15 |
> > sys-apps/855resolution and sys-apps/915resolution use arrays in |
16 |
> > config files, and there's not much way around it ATM if you want to |
17 |
> > replace multiple BIOS modes... |
18 |
> > |
19 |
> > <snip> |
20 |
> > # to replace more than one mode do something like this |
21 |
> > #replace=( |
22 |
> > # "4d 1280 768 24" |
23 |
> > # "5c 1400 1050 16" |
24 |
> > #) |
25 |
> |
26 |
> How about this? |
27 |
> |
28 |
> replace=" |
29 |
> '4d 1280 768 24' |
30 |
> '5c 1400 1050 16' |
31 |
> " |
32 |
> |
33 |
|
34 |
Actually, that may work better than my delimited with ; approach. |
35 |
We could then do |
36 |
|
37 |
eval set -- "${replace}" |
38 |
for x in "$@" ; do |
39 |
.... |
40 |
done |
41 |
|
42 |
Thanks |
43 |
|
44 |
Roy |
45 |
-- |
46 |
gentoo-dev@g.o mailing list |