RE: new cvs committer, some ideas

The one true way to fix this is to make sure that the paths are
associated with exmh() variables, and those are set in the main exmh,
exmh-bg, exmh-async scripts.  The exmh-based install scripts re-write
these driver scripts with user-supplied configuration information.  That
includes the #! Line that specifies wish. So, you must leave the #!wish
in the .MASTER files so that exmh_install will re-write them correctly.

Frankly, I'm not familiar with how the package maintainers
co-opt/work-around the built in installation schemes.  Just don't mess
it up :-)

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Neil W Rickert
Sent: Wednesday, June 18, 2008 7:02 AM
To: Alexander Zangerl
Cc: [email protected]
Subject: Re: new cvs committer, some ideas

Alexander Zangerl <[email protected]> wrote on Jun 18, 2008:

>* installation paths
>debian requires more strict adherence to the filesystem hierarchy
standard,
>which means for exmh that bitmaps, helper scripts, documentation and
>tcl code should not all end up in /usr/lib/exmh.

>the debian version uses /usr/share/exmh/bitmaps for guess what,
>/usr/share/exmh/ for scripts, 
>/usr/share/doc/exmh for documentation,
>/usr/lib/exmh for tcl code and /usr/bin/exmh for the executable.

The whole world is not debian.

Using subdirectories is not a problem.  Hard wiring those paths
to what debian uses will great problems for other users.

>* explicit paths in #!
>most scripts in the exmh package use unqualified interpreter names
>for wish (but not for /bin/sh, for whatever reason). personally i find
that
>a bad idea, and would very much suggest using /usr/bin/wish 
>and /usr/bin/expect explicitely. any comments on that?

No!  Hell no!

That will create headaches for people.

For example, on this system "wish" is installed as "/opt/tcl/bin/wish"
with a symlink "/usr/local/bin/wish" as the standard way of accessing
it.  If there is to be an interpreter name, then it needs to be
either "/usr/local/bin/wish" or "/opt/tcl/bin/wish" on this system.

The last thing I need, is to have to edit every exmh script whenever I
update to a new version.

You are looking at this from a vendor's perspective.  But you need to
also consider the after-market users who need to install exmh in a
place that makes it easily accessible, but which is clearly separated
from the vendor area of the file system.

 -NWR


_______________________________________________
Exmh-workers mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-workers