| 1 |
On Mon, Feb 10, 2014 at 12:20 PM, Tom Wijsman <TomWij@g.o> wrote: |
| 2 |
> On Mon, 10 Feb 2014 17:05:22 +0100 |
| 3 |
> Ulrich Mueller <ulm@g.o> wrote: |
| 4 |
>> The package manager must be able to uninstall old packages, which |
| 5 |
>> essentially means that support for old EAPIs cannot be removed. |
| 6 |
> |
| 7 |
> That's only a subset of the entire EAPI, which could be separately |
| 8 |
> still supported; while no longer supporting the majority of it, for |
| 9 |
> example, whether src_prepare is supported doesn't really matter anymore |
| 10 |
> when you are uninstalling a package. One could make up a list; however, |
| 11 |
> it's not a problem yet, it might become one in 10 years or so... |
| 12 |
|
| 13 |
Well, that strikes me as a cross-that-bridge-when-we-get-to-it |
| 14 |
problem. However, if maintaining the code becomes a problem we could |
| 15 |
always create a script that finds and re-installs any package that |
| 16 |
uses an about-to-be-desupported EAPI and then the system will be clean |
| 17 |
of them. It doesn't sound nearly as bad as that glibc upgrade that |
| 18 |
broke the ABI a decade ago, and it would only impact packages that |
| 19 |
hadn't been otherwise updated in a long time... |
| 20 |
|
| 21 |
Rich |
Archives