Freedoom is distributed by upstream with the intention to be run by a doom engine; this is also the expectation of end users. Freedoom documentation makes several recommendations for the GZDoom engine (and occasionally the Crispy Doom engine), so GZDoom should be the preferred engine is no other is available. See also Freedoom download page: https://freedoom.github.io/download.html See also Freedoom README.adoc: https://github.com/freedoom/freedoom/blob/master/README.adoc Reproducible: Always
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6dd37f121e4cecb95555fbcddcae382d089a4ca7 commit 6dd37f121e4cecb95555fbcddcae382d089a4ca7 Author: William Breathitt Gray <vilhelm.gray@gmail.com> AuthorDate: 2019-06-09 02:55:09 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2019-06-18 21:20:38 +0000 games-fps/freedoom: Add doom engine runtime dependency Freedoom is distributed by upstream with the intention to be run by a doom engine; this is also the expectation of end users. This patch adds a doom engine as a runtime dependency for Freedoom. Three possible doom engines are listed in RDEPEND: games-engines/odamex, games-fps/doomsday, games-fps/gzdoom. The games-fps/gzdoom package is set to preferred as it is the recommendation of the Freedoom upstream team. Closes: https://bugs.gentoo.org/687672 Package-Manager: Portage-2.3.67, Repoman-2.3.14 Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com> Signed-off-by: James Le Cuirot <chewi@gentoo.org> games-fps/freedoom/freedoom-0.11.3-r1.ebuild | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)
