Future EAPI/EAPI 5 tentative features

From Gentoo Wiki
Jump to:navigation Jump to:search

This is a working page that contains references to all features that have been suggested for EAPI 5.

Note
The Gentoo Council has accepted EAPI 5 in its 2012-09-11 meeting . The final wording can be found in the Package Manager Specification ( PDF ). This page is kept for historical and documentation purposes.

Accepted

Rejected

  • econf --disable-silent-rules ( see above )
    • Apply retroactively to EAPI 4?
    • Apply retroactively to all EAPIs? (May be problematic because of additional configure call.)
  • User patches
    Specification , Portage no-op dummy stub
    • Intrusive.
    • Current wording of the spec requires that every ebuild includes a call to the apply_user_patches function in src_prepare. An alternative would be to apply user patches after src_prepare as a default, if the ebuild doesn't call the respective function.
    • The spec doesn't provide any kind of epatch function, so we will end up having two copies of epatch, one for user patches, and the other (from eclass) for ebuilds.
    • Are we happy with the name apply_user_patches? (epatch_user? euserpatch?)
  • License groups in ebuilds
    bug #287192
    • A simpler solution would be create separate license files like GPL-2+ for the few cases where this is needed. This would have the advantage that it could be applied to all EAPIs.
  • Extended default list of extensions in dohtml
    bug #423245
    • Objections against inclusion of non-standard extensions like .ico have been raised.
  • Directories for use.* and package.* in profiles
    bug #282296
    • Need profiles EAPI bump
  • make.defaults etc.in ${repository_path}/profiles
    bug #414817
    • Need profiles EAPI bump
Retrieved from " /wiki/Future_EAPI/EAPI_5_tentative_features&oldid=1399486 "