Future EAPI/EAPI 6 tentative features

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

Unclassified

 * Bash 4.2


 * nonfatal die


 * get_libdir
 * Used in econf, but so far not available as separate PM function
 * Used in econf, but so far not available as separate PM function


 * Allow empty DOCS variable


 * Directory support for DOCS


 * Doc install function (edocs? einstalldocs?)


 * Query function for IUSE
 * Alternatively, or in addition, query IUSE_EFFECTIVE?
 * Alternatively, or in addition, query IUSE_EFFECTIVE?


 * failglob
 * In global scope only, or everywhere?
 * In global scope only, or everywhere?


 * PATCHES support in default src_prepare


 * Unpack .txz


 * Case-fold extensions in unpack


 * unpack accept absolute paths


 * Directory support for package* and use*

Some features rejected for EAPI 5

 * User patches
 * PMS wording, 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?)


 * EJOBS variable
 * 
 * Discussion was almost 4 years ago. Is there (still) consensus?
 * Discussion was almost 4 years ago. Is there (still) consensus?


 * Source eclasses only once
 * 
 * 


 * HDEPEND: host dependencies for cross-compilation