The following links on http://www.gentoo.org/proj/en/qa/pms.xml are inaccessible: eapi-2-approved-2008-09-25 (PDF) - http://distfiles.gentoo.org/distfiles/pms-2.pdf eapi-3-approved-2010-01-18 (PDF) - http://distfiles.gentoo.org/distfiles/pms-3.pdf Also, is pms-1 available? as there are a large number packages which still conform to this standard.
These files really shouldn't be on the mirrors, rather in a project space.
(In reply to comment #0) > The following links on http://www.gentoo.org/proj/en/qa/pms.xml are > inaccessible: > eapi-2-approved-2008-09-25 (PDF) - > http://distfiles.gentoo.org/distfiles/pms-2.pdf > eapi-3-approved-2010-01-18 (PDF) - > http://distfiles.gentoo.org/distfiles/pms-3.pdf I've updated these links to point to my dev space. Thank you for reporting this. > Also, is pms-1 available? as there are a large number packages which still > conform to this standard. The latest version includes all previous EAPIs, so old versions aren't really needed. I wonder if we shouldn't just keep the last version approved by the council and a recent snapshot from git. (Currently, that would be eapi-5-approved-2012-09-20 and HEAD.)
Thanks for fixing the 404. The reason I requested all versions of the EAPI documentation to be available, is mostly for academic purposes. Since each version is an enhancement of the previous version, it would be useful to read the EAPI1 documentation, review several EAPI1 ebuilds, and then compare these to EAPI2 documentation and ebuilds, to comprehend the different programming techniques. If I jump straight in at EAPI5, though I'll be able to program compliant ebuilds, I won't readily identify deprecated programming techniques in need of enhancement.
PMS documents every Council-approved EAPI, and it points out where the differences are. There's no need to read an earlier version to find out what earlier EAPIs look like.
