Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On 01/02/2011 05:19 PM, Jorge Manuel B. S. Vicetto wrote:
>
>
> One way we could drop EAPI 0 would be if we do a major review of tree
> and repo formats to improve upgrade paths, which would however likely
> require breaking backwards compatibility at such point.
> I believe such a change would only be acceptable, if we would pack
> enough features and safety measures that it would ensure another break
> would not need to be done for a long time.
>
It's quite likely that if you are currently on a system with Portage
that does not understand EAPI 1 there's so many obstacles along the
upgrade path that a clean install makes more sense. Maybe someone is
willing to test this so that we actually know if there is an upgrade
path from EAPI 0 available any more.
Regards,
Petteri
|
|
