* Jon Dowland wrote [31.10.10 13:26]: Hi, > However, shunit2 is a library, and should be packaged as such. Shipping a > binary in /usr/bin which is not meant to be executed, but rather sourced, > really isn't good.
Hm i thought this is the standard way to be able to have sourceable scripts without the need to specify the path. For example gettext-base ships gettext.sh in /usr/bin which behaves the same: $ gettext.sh GNU gettext shell script function library version 0.18.1 Usage: . gettext.sh Im sorry if this is not the right way to do it. I chose it because i thought it would be good if you don't have to specify the path of shunit2 and other software does the same ;0 So just drop the /usr/bin/shunit2 script and ship it in /usr/share/shunit2? > Do you intend to submit the patch upstream? The added file (/usr/bin/shunit2) is quite small and is a really small, specific, wrapper. I'll doubt if it is useful in upstream, especially since upstream does not have an install script, so IMHO it makes not much sense to add this wrapper to the project. regards, Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
