| 1 |
On Monday, July 11, 2011 20:38:49 William Hubbs wrote: |
| 2 |
> this bug was filed against OpenRc today [1]. The issue was that the user |
| 3 |
> was attempting to use bash arrays, which, as far as I knew are not |
| 4 |
> supported in OpenRc. |
| 5 |
|
| 6 |
they've been supported to ease migration from existing configs. |
| 7 |
|
| 8 |
> bash arrays are not documented anywhere as far as OpenRc is concerned. |
| 9 |
|
| 10 |
yes, but very little has been historically documented in openrc, so i wouldnt |
| 11 |
take that as a suggestion of intent. |
| 12 |
|
| 13 |
> Also, this is not a posix feature, so supporting it technically goes against |
| 14 |
> OpenRc's design. |
| 15 |
|
| 16 |
i dont think this logic follows. openrc's design is to be usable on top of |
| 17 |
POSIX shells, but not as a requirement. if you search the mailing list |
| 18 |
archives, i recall Roy having a thread on the topic of bash arrays. |
| 19 |
|
| 20 |
> I guess what I'm trying to figure out is, what is the technical |
| 21 |
> advantage for bash arrays as compared to using strings the way things |
| 22 |
> are shown in net.example? |
| 23 |
> |
| 24 |
> If there isn't one, would there be a lot of objections to me removing |
| 25 |
> this code? |
| 26 |
|
| 27 |
i dont think we've had openrc in stable long enough to force people to |
| 28 |
migrate. so i'd keep the code putting along for now, and add a note to the |
| 29 |
feature removal schedule only after we have checks in the openrc ebuild that |
| 30 |
to catch upgrade paths (and perhaps even do the migration for users). |
| 31 |
-mike |
Archives