-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EAPI=7 support #6
Comments
Can this feature be expected anytime soon? It's probably the last thing that obstructs paludis usage. Btw, I've rehosted your ebuild in my overlay (which is available in official listings), I hope you don't mind. |
Yes, I understand. Sure, I don't mind. |
The changes from EAPI 6 to EAPI 7 can be found in The ultimate guide to EAPI 7.
So all in all it seems there are only a few changes necessary to get to a working state with basic EAPI 7 support. Unfortunately I don’t think I can be of much help in implementing, as I’m completely unfamiliar with the codebase and I haven’t used c++ in years. If there is something to test though, I'll gladly try to do that. |
My own conclusions about EAPI7 are roughly the same. |
For those interested (read - those who are ready for testing/breakage). I've pushed new ebuild changes in https://github.com/MageSlayer/paludis-gentoo-overlay with "eapi7" use flag to enable experimental EAPI7 Paludis build. |
I am getting a lot of failures on EAPI 7 ebuilds like this one in xterm-337: All the errors reference different eclasses but mostly: autotools, mulitlib, multili-minimal. and distutils-r1 All the failures occur in: /usr/libexec/paludis/0/eclass_functions.bash:63 |
@hlandgarten |
Most install now. Still have issue on some ebuilds. For example rdesktop: All the ebuilds with this issue have multiple items in the inherit line. |
Ok. Thanks for testing. |
I currently have 20 ebuilds failing because of has_version so it would be good to get it implemented. Gentoo added lots of EAPI7 ebuilds. |
Yes, I know. |
I have also seen the
Besides that, it seems to work fine so far. Thank you for the progress on this! |
Glad someone else also appreciates this project. |
it's safe until we're cross-compiling related to MageSlayer#6
Stub the EAPI7 {best,has}_version features. Unit tests and proper support is still TODO Related to #6
The new version is working great. All my ebuilds are now building. Thank you for bringing paludis back to life. Maybe we can get it back in the gentoo tree. |
@hlandgarten |
it's safe until we're cross-compiling related to MageSlayer#6
…es) into build_depend(encies)_target and build_depend(encies)_host. Related to MageSlayer#6 Note that this implementation currently doesn't actually do any architecture checks. Instead, both dependency lists are merged together. It also breaks API (at least for the bindings), so a library version bump would be in order.
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
it's safe until we're cross-compiling related to MageSlayer#6
…es) into build_depend(encies)_target and build_depend(encies)_host. Related to MageSlayer#6 Note that this implementation currently doesn't actually do any architecture checks. Instead, both dependency lists are merged together. It also breaks API (at least for the bindings), so a library version bump would be in order.
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
Related to MageSlayer#6
it's safe until we're cross-compiling related to MageSlayer#6
…es) into build_depend(encies)_target and build_depend(encies)_host. Related to MageSlayer#6 Note that this implementation currently doesn't actually do any architecture checks. Instead, both dependency lists are merged together. It also breaks API (at least for the bindings), so a library version bump would be in order.
Corresponding Gentoo bug https://bugs.gentoo.org/655976
The text was updated successfully, but these errors were encountered: