1 |
>>>>> On Sat, 9 Jan 2010, Ciaran McCreesh wrote: |
2 |
|
3 |
>> | Vote (6 yes, 1 no): Ebuilds must be completely parsable with |
4 |
>> | =bash-3.2*, any use of later bash features will be reverted. |
5 |
|
6 |
> Doesn't the way that's worded mean "it has to work with every single |
7 |
> 3.2 patch", though? I take that to mean "must be completely parsable |
8 |
> with bash-3.2_p0 through bash-3.2_p9999", not "must work with at |
9 |
> least one version of bash-3.2_psomething". |
10 |
|
11 |
Then we could simply have said "must be parsable with =bash-3.2" which |
12 |
we didn't. Clearly, the main idea was to disallow usage of bash-4* |
13 |
features. We could also discuss if "use of features" includes things |
14 |
mentioned in the documentation but not properly working because of |
15 |
bugs. Anyway, I think that tweaking the spec's wording wouldn't have |
16 |
many practical consequences. |
17 |
|
18 |
But we may have to revert that eclass for a different reason: |
19 |
The council has voted (in the same meeting) that an upgrade path for |
20 |
stable systems must be provided for one year at least. One year ago |
21 |
bash-3.2_p33 was the latest stable version, therefore we must not yet |
22 |
rely on any bugfixes in _p48. |
23 |
|
24 |
Ulrich |