| 1 |
On Thu, 30 Aug 2012 23:58:00 +0000 (UTC) |
| 2 |
Duncan <1i5t5.duncan@×××.net> wrote: |
| 3 |
> Of course an individual PM could choose to keep support for as long |
| 4 |
> as they want, but unless I'm missing something, that'd let PMs drop |
| 5 |
> support for old EAPIs if desired, with at least a reasonably sane |
| 6 |
> upgrade path for both PM devs and users. |
| 7 |
|
| 8 |
It's irrelevant: the amount of package mangler code to be saved by |
| 9 |
removing old EAPIs is so small it's not worth discussing. Most EAPI |
| 10 |
changes so far have either been additions or very simple behaviour |
| 11 |
tweaks, not removals of annoying things. |
| 12 |
|
| 13 |
There are things we might change in future EAPIs that will in the very |
| 14 |
long term make this discussion worthwhile. If we get rid of VDB access |
| 15 |
or unconstrained env saving, *then* it might be worth having this |
| 16 |
discussion. |
| 17 |
|
| 18 |
-- |
| 19 |
Ciaran McCreesh |
Archives