The file you have downloaded is called
drjr.ARCH.tar.gz, where ARCH is
replaced by the name of your architecture (eg,
i386-linux for Linux or sparc-solaris
for Solaris on a Sparc architecture).
gunzip utility:
gunzip drjr.ARCH.tar.gz
The gzip utility can simulate gunzip with
the -d file. If you don't have gzip, you
can obtain it from the GNU
archive. Once you have uncompressed the distribution, you should
have a file called drjr.ARCH.tar.
tar
command:
tar -xvlf drjr.ARCH.tar
This will create a directory called plt/ in the current
directory.
/usr/local/lib/plt/. If you
cannot or do not wish to use that location, you may pick any other
(including, say, one of your own directories). Move the
plt/ directory into its final destination, e.g.,
mv ./plt /usr/local/lib/
drjr.ARCH.tar) using rm.
If you're low on disk space, you can do all this in a single step. For instance, the default configuration can be obtained thus:
cd DESTINATION
gzcat LOCATION/drjr.ARCH.tar.gz | tar -xvlf -
rm LOCATION/drjr.ARCH.tar.gz
where LOCATION denotes the location of the
compressed file and DESTINATION is the
destination directory. If gzcat is not defined for your
system it can be performed by gzip using the
-cd flag.
./install while the current directory is
plt/. This will modify the scripts in
plt/bin/ (based on the full pathname of the current
directory) and will create .zo files (for faster
startups). All files are created within the plt/
directory hierarchy.
plt/bin/.
Thus, you
might wish to include /usr/local/lib/plt/bin/ or
${PLTHOME}/bin/ in your PATH (as
appropriate).
If you have root priviledges, you could instead create links from some
standard directory to the executables. For example, if you put the
distribution in /usr/local/lib/plt, you could add these
links:
cd /usr/local/bin
ln -s /usr/local/lib/plt/bin/drscheme-jr .
ln -s /usr/local/lib/plt/bin/mzscheme .
ln -s /usr/local/lib/plt/bin/mzc .
| PLT / scheme@cs.rice.edu |