[GRASS5] New initialization code
jhickey at hpcc.nectec.or.th
Sun Dec 3 22:40:03 EST 2000
Eric Mitchell wrote:
> Andreas Lange wrote:
> > Hi,
> > Eric Mitchell wrote:
> > > On Unix systems, "ln -s `which wish` $GISBASE/bin/grasswish".
> > > Any desired wish could be used, configure could take a
> > > --with-wish=/path/to/mywish argument for configurability,
> > > or check for "wish, wish8.0, etc." for known working versions.
> > I think that this has the problem that it must be implemented
> > somehow with the install script too, as re-compiling should be (at
> > least for linux) the exeption, not the standard.
> As long as all of grass's Tcl/Tk scripts reference "grasswish"
> in their restart-in-wish line, you'd just have to change which
> wish is referenced by the symbolic link. You wouldn't have to
> recompile any code, unless tcltkgrass depends on a custom Tcl
> interpreter, but that would require a recompile to use a
> different Tcl interpreter anyway.
> > > This way, the user can update their wish, and grass doesn't
> > > necessarily rely on a particular version of wish, just a link
> > > from (or copy in) $GISBASE/bin/grasswish to the "real" wish.
> > This may cause problems for people who have no root access to the
> > machine they want to install grass on.
> No more of a problem than trying to install grass itself. They
> could install it under their home directory, assuming they have
> the space. Which means they could always overwrite it if they
> need to. You could even have your own grasswish link/executable
> in your PATH before the grass-installed one. (e.g. ~/bin).
Thank you very much for your suggestion Eric, but in this case I think
we should keep things as simple as possible. Therefore, I will just
search for wish in the users path. I think this is a reasonable
assumption since many Tcl/Tk scripts either have something like
#!/usr/bin/wish or the "next line restarts with wish" trick, thus
sysadmins would have to create the appropriate link for other software
as well. If wish is not in the user's path I plan to print an
> > I don't know, i think it should be up to Justin and/or Markus to
> > decide how it should be done.
> Agreed, I'm just throwing ideas out there. My company's main
> product where I work does a lot with Tcl/Tk and custom wish
> interpreters, so I was offering some of the ideas we've tried
> that might work for grass.
Please continue throwing your ideas our way, in fact I may be in touch
with you concerning custom wish interpreters in the future if you
wouldn't mind. I am considering using one for the "real" new
initialization work, but haven't quite decided yet. However, it will be
a little while before I get to that point. I'll let you know.
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey at hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'
More information about the grass-dev