This installation has been tested under both the Debian potato and
RedHat 6.2 distributions of Linux. 

(1) Install Yorick version 1.4.  Tarballs, rpm's, and debs for yorick-1.4
are available from ftp://ftp-icf.llnl.gov/pub/Yorick/doc/download.html.
Yorick is an official part of the Debian distribution of Linux (in fact
the packager is also the Yorick maintainer) so you can also find these
debs at http://www.debian.org/distrib/packages or via the usual apt-get
or dselect methods of downloading and installing official debian packages.

Under RH 6.2 we have only tested yplot against the rpm version of yorick-1.4
and similarly under Debian we have only tested against the official
yorick-1.4 package.  If instead you do a tarball install of yorick-1.4 into
/usr/local, then you will have to modify (by adding to the directories
searched) Makefile.build.in to find yorick on your system.

Note, the current yPlot takes advantage of the improved procedure for embedding
foreign code in yorick-1.4 and will not work with yorick-1.1, 1.2, or 1.3.
The above sources also have packages for the very first release of yorick-1.5,
but we haven't tested how well yplot works with that version yet.  

(2) Install PLplot-5.0.4 (no earlier version will work properly).  This
package has been released at http://sourceforge.net/projects/plplot/ (click
on download).  At that site you will be able to obtain a tarball and a small
variety of rpm's. Note the latest debs are for PLplot-5.0.2 (although
hopefully that situation will soon change) so Debian users should use the
tarball release of 5.0.4 instead.

When building and installing PLplot from tarballs make sure you use (at least)

./configure --with-double=yes --prefix=/usr/local/plplot

The double precision is required by yPlot, and the current install procedure
for yPlot assumes that prefix (or prefix=/usr for rpm packages). If
installing PLplot from rpm's (and eventually debs), this configuration issue
is taken care of automatically.

(3) This step can be done as an ordinary user (we use Makefile.build* files
here rather than Makefile* files because as part of the build procedure
yorick produces a file called Makefile which would name clash!)

#build configure from configure.in.  (This step necessary from CVS version,
but tarball version has configure included already.)

autoconf

#build Makefile.build from Makefile.build.in.  (This step always necessary.)

./configure --prefix=/usr/local/yplot

Note if you specify no prefix then the default prefix value is /usr/local
and your yplot files get mixed in with everything else in /usr/local rather
than being in their own unique tree that can be deleted without interfering
with anything else.  deb's (when those get made) and rpm's, of course, install
into a prefix of /usr, but this is not recommended if you are just doing
a tarball install because the file mixing problem gets even worse.

(4) As an ordinary user:

make -f Makefile.build

This creates in the current directory the following executables:

(i) yplotl (yorick front-end to vanilla PLplot.  The "l" suffix refers to the
default landscape mode of PLplot [and yplotl].)  

(i) yplot (yorick front-end to PLplot where the PLplot -portrait mode [which
currently only affects ljii, ljiip, psc, ps, and pstex devices] is turned
on just before plinit is called.)  This version of yplot corresponds to the
traditional portrait-mode yplot (albeit with more devices in portrait mode).

The above make command
also builds doc/yplot.doc, all the doc/demo?.ps files, the
doc/plpoin.ps and doc/plsym.ps.1 through doc/plsym.ps.17 files, all the
x??.ps files corresponding to the x??c examples from PLplot, portrait-mode
versions of those files x??p.ps, and the
documentation doc/ytut.[dvi, ps.gz].

Note, the live web site documentation was installed from this generated
yplot-1.1 documentation by AWI using

scp -p doc/ytut.ps.gz airwin@shell1.sourceforge.net:/home/groups/y/yp/yplot/htdocs

(the -p preserves the permissions among other things which should be
rw-rw-r--)

The possibility of installing the dvi form of the documentation on the live
web site was also considered but rejected since it refers to the postscript
demo, plpoin, and plsym files which would also have to be bundled with it.

(5) As the super-user 

make -f Makefile.build install

Alternatively you could use 

make ROOT=/tmp/build_area -f Makefile.build install 

to allow the package to be built by an ordinary user in /tmp/build_area (or
any other user-writable area such as $RPM_BUILD_ROOT used, e.g., in spec
files when making rpm's).

Alan W. Irwin <irwin@beluga.phys.uvic.ca>
Conrad Steenberg <conrad@hep.caltech.edu>
2001 June 18
