Perhaps
src/general/init/Gmakefile
should
1. store the "grass5" script into GISBASE (instead of UNIX_BIN)
2. then copy from GISBASE to UNIX_BIN
When installing as user:
Then the grass5install.sh can get this script from GISBASE
(out of the tar package) and put into UNIX_BIN. This simplifies
the grass5install.sh section.
What do you think about this idea?
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
Perhaps
src/general/init/Gmakefile
should
1. store the "grass5" script into GISBASE (instead of UNIX_BIN)
2. then copy from GISBASE to UNIX_BIN
When installing as user:
Then the grass5install.sh can get this script from GISBASE
(out of the tar package) and put into UNIX_BIN. This simplifies
the grass5install.sh section.
What do you think about this idea?
Pretty good idea, the only problem would be changing the line
GISBASE=/usr/local/grass5
The idea I had was to use awk in the binaryInstall.src file to create
the proper echo commands in the grass5install.sh file. I'll look into
both ideas to see what I can come up with.
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
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@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Dec 07, 2000 at 10:03:55AM +0000, Markus Neteler wrote:
Hi Justin,
a proposal concerning the grass5 start script:
Perhaps
src/general/init/Gmakefile
should
1. store the "grass5" script into GISBASE (instead of UNIX_BIN)
2. then copy from GISBASE to UNIX_BIN
When installing as user:
Then the grass5install.sh can get this script from GISBASE
(out of the tar package) and put into UNIX_BIN. This simplifies
the grass5install.sh section.
What do you think about this idea?
Me again.
An addition: Above proposal should be postponed for the next release
as we would have to publish a new tarball.
Do you think it's feasible *this* time to solve the problem by only
updating the install script?
If not, we directly go for beta10 today/tomorrow...
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
An addition: Above proposal should be postponed for the next release
as we would have to publish a new tarball.
Do you think it's feasible *this* time to solve the problem by only
updating the install script?
If not, we directly go for beta10 today/tomorrow...
As I said in my previous message, I'll let you know. That's why I was
looking at the awk solution since it did not effect the tarball.
Talk to you soon, on to testing.
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
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@geog.uni-hannover.de with
subject 'unsubscribe grass5'