From e98d27c650db7c4fc3d4969c956c55d6f043efb0 Mon Sep 17 00:00:00 2001 From: Ned Ludd Date: Fri, 14 Mar 2008 01:47:23 +0000 Subject: [PATCH] - clarify exactly when EAPI > 0 should and should not be used. solar/Betelgeuse --- skel.ebuild | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/skel.ebuild b/skel.ebuild index 0d306700e794..5cef70d6704b 100644 --- a/skel.ebuild +++ b/skel.ebuild @@ -12,11 +12,13 @@ # generated to contain the correct data. # The EAPI variable tells the ebuild format in use. -# Defaults to 0 if not specified. See current PMS draft for more details. +# Defaults to 0 if not specified. The current PMS draft contains details on +# a proposed EAPI=0 definition but is not finalized yet. It is for this +# reason that using EAPI > 0 should be avoided. # Eclasses will test for this variable if they need to use EAPI > 0 features. -# Ebuilds should not define EAPI=1 unless they need to use features added -# in that version. -#EAPI=1 +# Ebuilds should not define EAPI > 0 unless they absolutely need to use +# features added in that version. +#EAPI=0 # inherit lists eclasses to inherit functions from. Almost all ebuilds should # inherit eutils, as a large amount of important functionality has been -- 2.26.2