checking out any current repoman version tag puts portage
into a version where EAPI 8 support is not enabled
Signed-off-by: Theo Anderson <telans@posteo.de>
Without the -V flag to enable version sort, 'sort' can falsely identify
a version string like 3.0.9 to be greater than 3.0.10. This can be
shown by running 'git tag | grep portage | sort -u' in the Portage Git
tree. This issue is not so prominent for repoman yet because the latest
version of repoman as of now is 3.0.3, but it will surface when repoman
3.0.10 is released.
Signed-off-by: Yuan Liao <liaoyuan@gmail.com>
Closes: https://github.com/gentoo/sci/pull/1094
Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org>
Reduce code duplication by moving the ::gentoo setup part
into a seperate script. This way only one file has to be
edited when e.g. updating the profile to a new version
Signed-off-by: Andrew Ammerlaan <andrewammerlaan@riseup.net>
By using a seperate script instead of running everything in the yml
file, we gain the ability to use and manipulate variables. This
means that we can now automatically run the latest version of
repoman, which should make this more hands-off by removing the
need to update this every now and then.
Signed-off-by: Andrew Ammerlaan <andrewammerlaan@riseup.net>
- add self as maintainer
- update variable names
- un-nest for loops
- check for matching package name before starting loops
- speed improvements: ~3s vs 5m
Package-Manager: Portage-3.0.14, Repoman-3.0.2
Signed-off-by: Theo Anderson <telans@posteo.de>
