Many of the eclass files in portage-stable aren't recent enough to include support for EAPI 7 and die with "Unsupported EAPI version" if used in a EAPI 7 ebuild. We should update our eclass files to more current upstream versions to allow usage of EAPI 7.
Known eclass files that need to be updated:
distutils-r1
multibuild
python-r1
udev
Many of the eclass files in portage-stable aren't recent enough to include support for EAPI 7 and die with "Unsupported EAPI version" if used in a EAPI 7 ebuild. We should update our eclass files to more current upstream versions to allow usage of EAPI 7.
Known eclass files that need to be updated:
distutils-r1
multibuild
~python-r1~
~python-any-r1~
~python-single-r1~
udev
Many of the eclass files in portage-stable aren't recent enough to include support for EAPI 7 and die with "Unsupported EAPI version" if used in a EAPI 7 ebuild. We should update our eclass files to more current upstream versions to allow usage of EAPI 7.
Known eclass files that need to be updated:
distutils-r1
multibuild
--python-r1--
--python-any-r1--
--python-single-r1--
udev
Many of the eclass files in portage-stable aren't recent enough to include support for EAPI 7 and die with "Unsupported EAPI version" if used in a EAPI 7 ebuild. We should update our eclass files to more current upstream versions to allow usage of EAPI 7.
Known eclass files that need to be updated:
distutils-r1
multibuild
udev
Updated:
python-r1
python-any-r1
python-single-r1
Comment 1 by cjmcdonald@chromium.org
, Dec 27