Issue metadata
Sign in to add a comment
|
Support EAPI v6 in ChromeOS SDK |
||||||||||||||||||||||||
Issue descriptionRecent upstream Gentoo configs use EAPI 6. Example: https://gitweb.gentoo.org/repo/gentoo.git/tree/sec-policy/apparmor-profiles/apparmor-profiles-2.10.1.ebuild Such packages cannot be imported in portage-stable using cros_portage_upgrade, because "equery which <package name>" cannot locate the ebuild, presumably because the SDK uses EAPI 5. Even after manually copying the package to ChromeOS tree, it cannot be built as-is because the SDK uses EAPI 5. Please upgrade the SDK to use EAPI 6.
,
Jul 27 2016
,
Sep 1 2016
,
Jan 17 2017
Taking a look, so how much effort it is to update portage, repoman and see how older ebuild are braking. So far, we are hitting https://github.com/gentoo/portage/commit/b830bbc3b10bf239611663d0572b2cd4ba3d656a while emerging gcc: use() calls are not allowed in global scope
,
Jan 18 2017
,
Feb 15 2017
Hello gwendal@, were you able to make progress on this? Was bug 682455 the only issue that's blocking it?
,
Feb 16 2017
,
Mar 29 2017
,
Apr 24 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by adityakali@google.com
, Jul 26 2016Labels: -Pri-3 Pri-2