* Jon Dowland wrote [26.03.12 17:17]: > You mention in the latest changelog that your local wrapper script was > replaced > by an upstream one. However, it doesn't look different, and I can't find the > script in the upstream source tarball or version control system. > So I wonder if you closed the wrong bug, or wrote the wrong summary, > or forgot the right wrapper in the last upload? It was by intention as it is different. The shunit2 script in /usr/bin can be executed directly from the command line. You are now able to do something like
,---- | shunit2 /path/to/unit/file `---- This was done by upstream. So for now i install the shunit2 script into /usr/bin and add a symlink from /usr/share/shunit2/shunit2 If you don't have any objections i would close this bug as the shunit2 script in /usr/bin can now be executed directly without the need to source it and can be useful. > Regarding the wrapper itself, and putting library code in /usr/bin: > > > 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: > > I was not aware that gettext-base did this, but afaik it is also incorrect to > do so. I think it might be worth discussing the technique on debian-devel. Feel free to start a discussion on debian-devel. But imho this shouldn't be a problem as long as the script/library prints a warning/notification if it is not sourced. cheers, Ulrich -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
