On Sun, May 15, 2016 at 07:48:27PM -0300, Tiago Ilieve wrote:
> There's one use case I can think of where overriding a
> "binary-without-manpage" is fine: if the executable isn't supposed to
> be used by the end-user, only as an external command called from the
> application itself.
In this case the binary should go into /usr/lib instead. That place
exist exactly for this reason:
"/usr/lib includes object files, libraries, and internal binaries that
are not intended to be executed directly by users or shell scripts"
http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA
Given that in your case you say the binary is not called by anything
else than the application itself, then why keep it in /usr/bin?
> Can't say if this is what is happening here, as I didn't reviewed the
> package.
Not here. This package puts a single ./usr/bin/HDFCompass in a package
named hdf-compass. If that's not intended to be used by the user then
I'd be really confused :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature