Your message dated Sat, 14 Jun 2008 18:23:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line This bug should be closed
has caused the Debian Bug report #372635,
regarding Binary executables not in standard PATH
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]

Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gmt
Version: 4.1.2-1


The executables are now installed in /usr/lib/gmt/bin. This directory is
not in a user's PATH. So, it simply and completely breaks old scripts.

One could argue that users now have to use "GMT command" instead of
"command", in this case, the answer is that if the binary files are
in /usr/bin, users CAN use either syntax, AND  it does not break years
of habits and old scripts.

Hope this makes sense

Christophe Martin.

--- End Message ---
--- Begin Message ---
I agree with Torsten that having 120 more binaries in /usr/bin which
pollute the global name space is not a good thing to do. Also upstream
already provides a GMT wrapper, and people could always manage
to add /usr/lib/gmt/bin to their own or global path to avoid breakages
of third-parties scripts (and that cannot be done viceversa if binaries
were placed into /usr/bin). 
Also I fixed GMT wrapper to apply that trick in place when calling  
and upstream recently fixed also examples scripts to work correctly
with binaries out of system PATH.

So I'm now closing this bug.

Francesco P. Lovergine

--- End Message ---
Pkg-grass-devel mailing list

Reply via email to