dev-java/fop uses a slotted name (e.g. fop-28) for the created executable and does not provide a name without the slot number. Currently there is only one ebuild for this package. It would be nice to have a non-slotted binary name by either: - create a non-slotted name for the binary -or- - have an eselect-fop that allows the selection of slotted executable. There are existing gentoo ebuilds that depend on fop, and looking at how they use fop, they are expecting just the name 'fop' Reproducible: Always Steps to Reproduce: 1. Install dev-lang/fop Actual Results: /usr/bin/fop-28 Expected Results: /usr/bin/fop
Additional info. It appears that upstream fop documents just using "fop" https://xmlgraphics.apache.org/fop/trunk/running.html
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=51e4a8e33be9e937113facc0d0ab65363a7de0de commit 51e4a8e33be9e937113facc0d0ab65363a7de0de Author: Volkmar W. Pogatzki <gentoo@pogatzki.net> AuthorDate: 2024-12-16 20:50:49 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2024-12-20 11:02:28 +0000 */*: slotmove dev-java/fop 2.8 0 #946557 forgot this when bumping to 2.10 Closes: https://bugs.gentoo.org/946557 Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net> Closes: https://github.com/gentoo/gentoo/pull/39740 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> dev-java/fop/{fop-2.10.ebuild => fop-2.10-r1.ebuild} | 4 ++-- .../logtalk/{logtalk-3.47.0-r1.ebuild => logtalk-3.47.0-r2.ebuild} | 2 +- net-fs/openafs/{openafs-1.8.13.ebuild => openafs-1.8.13-r1.ebuild} | 2 +- net-fs/openafs/{openafs-1.8.7.ebuild => openafs-1.8.7-r1.ebuild} | 2 +- .../openafs/{openafs-1.8.8.1-r1.ebuild => openafs-1.8.8.1-r2.ebuild} | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-)
