[Debian-med-packaging] Bug#1120150: hmmer: Ship easel miniapps instead of easel source code.
Charles Plessy
plessy at debian.org
Thu Nov 6 03:09:31 GMT 2025
Package: src:hmmer
Hi all,
HMMER ships the Easel library in its released tarball as it compiles on it. In
addition, this library has a collection of small command-line tools called
miniapps, which can be used for manipulating files typically used or produced
by HMMER.
AI tools are good at digging in old documentations or discussion forums and
suggest the use of old tools, which is how I got aware of the miniapps…
Currently our hmmer-examples packages ships the source code of Easel; I do not
know why.
I propose that the hmmer package starts to ship the miniapps; this can be done
with the following patch.
--- a/Makefile.in
+++ b/Makefile.in
@@ -129,6 +129,7 @@
if [ ! -d ${DESTDIR}${bindir} ]; then ${INSTALL} -d ${DESTDIR}${bindir}; fi
if [ ! -d ${DESTDIR}${man1dir} ]; then ${INSTALL} -d ${DESTDIR}${man1dir}; fi
${MAKE} -C src install
+ ${MAKE} -C ${ESLDIR} install
${MAKE} -C documentation install
# install-strip: same as install, but strip binaries
The command names all start with `esl-`, limiting the risk of name
collisions in the future.
If nobody remembers the reason why we ship the source code of Easel in the
examples package, I propose to stop doing it, or limit what we ship to the
documentation of Easel.
I can do it myself but I would be keen to hear your thoughts.
Have a nice day!
Charles
--
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from home https://framapiaf.org/@charles_plessy
- You do not have my permission to use this email to train an AI -
More information about the Debian-med-packaging
mailing list