Higan v107 was released on December 21, 2019: https://byuu.org/posts/higan-v107 Reproducible: Always
Higan v108 was released on 03 March 2020 and should be used instead of v107. https://byuu.org/download/higan/higan_v108-source.zip
I would be happy to work on ebuild changes here and test it out on my dev machine if that would be helpful. Then a member of the Games group can commit it to the tree. Please let me know if that would be helpful; otherwise, I don't want to step on anyone's toes.
You're a dev so I trust you to do a good job but at the same time, it's an unusual package and it needs an EAPI bump. A patch here so that I can immediately see the changes would be most helpful. Then you can push the commit yourself.
I haven't looked that much into it, it may be worthwhile to investigate the new "byuu" emulator project: https://byuu.org/posts/new-emulator-byuu For now the author expects to continue development on higan as well, but I'm not sure if this new project will replace higan in the future.
Higan v110 was released on March 20, 2020: https://github.com/higan-emu/higan/archive/v110.tar.gz Th original author, Near (formerly known as byuu), has stepped down and transferred ownership of the project to a new development team: https://byuu.org/articles/farewell Higan development and releases will now take place on the new git repo: https://github.com/higan-emu/higan
FYI just to keep up with all the forking: The original author, Near, forked higan again in April 2020; the project was renamed to ares and released under a more permission license (ISC license): https://github.com/ares-emu/ares Near stopped developing this fork in July, and the higan community intends to merge the work back into the higan master branch: https://github.com/ares-emu/ares/issues/8
ping
I think ares has been merged back into higan so it looks like v115 is the latest release now: https://github.com/higan-emu/higan/releases/tag/v115 Nathan Zachary, are you still working on an ebuild, or have you abandoned that effort?
I'm going to write an ebuild for v116 (upcoming release) if no one working on this already.
I apologise, but I haven't had time to work on an ebuild here because I've been preparing for exams. I had started working on an ebuild for byuu (an alternative project for Higan), but it looks like shifting to Higan for v116 would be the best approach. Thank you for offering to work on a new ebuild. Cheers, Nathan Zachary
I wrote an ebuild for the higan nightly pre-release because the higan v116 release date has not yet been chosen; when v116 is released I can submit an appropriate version bump. This pre-release ebuild also seems to have some minor issue that I'm having trouble resolving. If anyone has a chance, please check it out and comment if you have an idea what's causing the issue.
(In reply to William Breathitt Gray from comment #11) > This pre-release ebuild also seems to have some minor issue that I'm having > trouble resolving. If anyone has a chance, please check it out and comment > if you have an idea what's causing the issue. What is the issue that you're having with the ebuild?
(In reply to Nathan Zachary from comment #12) > (In reply to William Breathitt Gray from comment #11) > > This pre-release ebuild also seems to have some minor issue that I'm having > > trouble resolving. If anyone has a chance, please check it out and comment > > if you have an idea what's causing the issue. > > What is the issue that you're having with the ebuild? When the `make` call is invoked via emerge, it has trouble finding the appropriate directory, but the same line executed manually in the source directory completes without error. So my suspicion is that I am misconfiguring the path for `emake` in the ebuild.
Unless I'm just missing it, I don't see your ebuild attached here. I can take a look as time allows. Since v116 still hasn't been released, we probably have some time to troubleshoot. Cheers, Nathan Zachary
(In reply to Nathan Zachary from comment #14) > Unless I'm just missing it, I don't see your ebuild attached here. I can > take a look as time allows. Since v116 still hasn't been released, we > probably have some time to troubleshoot. > > Cheers, > Nathan Zachary It's on GitHub: https://github.com/gentoo/gentoo/pull/18503
I was able to resolve the issue I was having so the pull request on Github should be ready for reviewing now. One possible improvement to consider is whether we should define the emulation cores similar to how app-emulation/qemu handles it: by using QEMU_SOFTMMU_TARGETS rather than regular USE flags. Would it make sense to define something similar for games-emulation/higan, or leave the core selections as individual USE flags?
FYI, the "byuu" interface has been dropped and higan has returned to having just one user interface: https://github.com/higan-emu/higan/issues/7#issuecomment-774651819
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff0791015fac652c4e28fac9ff00dd805a75369b commit ff0791015fac652c4e28fac9ff00dd805a75369b Author: William Breathitt Gray <vilhelm.gray@gmail.com> AuthorDate: 2020-10-31 14:44:54 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2021-04-04 13:19:43 +0000 games-emulation/higan: Version bump to 116_pre20210404 Closes: https://bugs.gentoo.org/709674 Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/18503 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> games-emulation/higan/Manifest | 1 + games-emulation/higan/higan-116_pre20210404.ebuild | 101 +++++++++++++++++++++ games-emulation/higan/metadata.xml | 6 +- 3 files changed, 107 insertions(+), 1 deletion(-)
