[Debian-med-packaging] Bug#826684: /usr/bin/spin in "staden" and /usr/bin/spin in "spin"

[tony mancill]

Hello,

I'm not familiar with staden, but am taking a look at it and see that
/usr/bin/spin is symlinked -> /usr/bin/gap4, and that is essentially a
wrapper script that run things from /usr/lib/staden/bin/ (or BINDIR).

I also noticed that invoking "staden" returns a list of those file in
the BINDIR, so invoking "staden spin" would still work without a
/usr/bin/spin file shipped with the staden package.  Of course, there's
still the question of the manpage.

For the "spin" binary in the "spin" package, there isn't such a
mechanism available, so it would be more of a "think of a suitable name
and update the Debian documentation and README appropriately" exercise.

I assume "spin" has been called "spin" since its inception in staden
[1], and it's the same for the spin package [2].  Both projects appear
active and viable, so I see this as a question of trying to make a
sensible choice for our users (which I see as the choice that causes the
least confusion and disruption).  However, I don't pretend to know what
that is, I'm just hoping to start the conversation around this bug.  It
seems like the packages aren't likely to be co-installed, but my
understanding is that policy frowns upon simply having them conflict
with each other.

Is there any chance the staden maintainers would consider renaming the
wrapper in /usr/bin to "spin-gui" or something similar?  Or perhaps spin
(software verification) might become spin-verify?

Thank you,
tony

[1] http://staden.sourceforge.net/
[2] http://spinroot.com/spin/whatispin.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20160611/c1f7c789/attachment.sig>