Package: monkeysign Version: 0.8 Severity: important Control: found -1 0.7.1
I have had two unrelated cases of people asking me "where is the monkeysign binary"? People installing the monkeysign package expect a monkeysign script to be callable from the commandline. This seems like a fair expectation that was broken in 0.5 at the request of other Monkeysphere developers, to avoid conflicts with commandline completion. I believe, however, that this is not worth it, and will work towards restoring the original binary names. I am thinking of operating the following renames: 1. msign-cli -> monkeysign 2. msign -> monkeyscan Those reflect more clearly what each script does: monkeysign really does only signing, while monkeyscan focuses on qrcode scanning while also allowing to scan the key after. This also emphasises that the former functionality is better tested and more complete. Ideally, once monkeyscan evolves to have all the functionalities of monkeysign, the two can be merge and (say) a -c option (or the lack of a $DISPLAY) can make monkeysign stay on the commandline. But this is clearly not the case right now. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages monkeysign depends on: ii gnupg 1.4.12-7 ii python 2.7.3-4 Versions of packages monkeysign recommends: ii python-gtk2 2.24.0-3+b1 ii python-qrencode 1.01-2+b1 ii python-zbar 0.10+doc-8 ii python-zbarpygtk 0.10+doc-8 monkeysign suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
