[Axiom-developer] RE: Mark Botch

[Page, Bill]

Tim,

I think

  make install

usually installs to a directory that is already
in (or expected to be in) the user's path. E.g.
/usr/local/bin ... etc. This directory is specified
during the ./configure or defaulted. Thus the
install often requires root priveleges.

In many packages it is possible for a user to run
the built application without an install, but of
course then the user must expect to modify their
path manually or at least cd to the appropriate
bin directory first. E.g.

  cd axiom/mnt/linux/bin
  axiom

So I guess the best thing would be to have the
build initially set

  export AXIOM=${SPAD}/mnt/${SYS}

and also copy it into the mnt/linux/bin/axiom script
so that the user could run without installing.

Then during

  make install

the entire mnt/linux/bin directory could be copied
to the final target install directory and the 'axiom'
script could be updated with the correct location
and stored in the target directory.

At least I think that's how it usually goes ...

Regards,
Bill Page.

> -----Original Message-----
> From: Tim Daly [mailto:address@hidden
> Sent: Wednesday, October 29, 2003 2:41 PM
> To: address@hidden
> Cc: address@hidden
> Subject: Mark Botch
> 
> 
> Bill,
> 
> The latest CVS has "make install" but it is not complete.
> I can't decide how to put the Axiom shell script on your PATH.
> If the "make install" knows the install location and the SYS type
> we can modify the Axiom script to automatically set the AXIOM 
> variable. 
> 
> I have to figure out how other systems handle this problem.
> 
> Tim 
>