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
Looks like after today's council meeting we finally know what's in
EAPI 4:
It contains everything mentioned as EAPI 4 features in PMS, but with
the following differences:
Excluded / postponed to next EAPI:
- slot operator dependencies
- profile defined IUSE injection
Additionally included:
+ REQUIRED_USE (bug 347353)
+ MERGING_FROM (bug 347351)
How should we proceed now? Should we move the two excluded features
off to a branch (like eapi-5), and keep only EAPI 4 things in master?
Ulrich
|
|
