1 |
>>>>> On Fri, 18 Sep 2009, Ciaran McCreesh wrote: |
2 |
|
3 |
> No, the change can't be made without breaking the upgrade path. Users |
4 |
> who have an old EAPI 0 system with bash 3.0 installed need to be able |
5 |
> to upgrade it, and they can't do that if they can't source ebuilds. The |
6 |
> impact of the change you're suggesting has to be considered, and it's |
7 |
> not a simple decision to make. |
8 |
|
9 |
Some relative timing of events may be interesting here: |
10 |
12 May 2007 bash-3.2_p15 stable on major architectures. |
11 |
19 Aug 2008 python-2.3.6-r6 removed, which was the last ebuild |
12 |
of Python with EAPI 0. |
13 |
|
14 |
So the upgrade path for EAPI 0 systems is broken anyway, for a |
15 |
different reason. |
16 |
|
17 |
And if we stay at bash-3.0, then we should probably add its ebuild to |
18 |
the tree again, in order to ease compatibility testing. It was removed |
19 |
half a year ago. |
20 |
|
21 |
Ulrich |