Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!tut.cis.ohio-state.edu!sei.cmu.edu!fs7.ece.cmu.edu!o.gp.cs.cmu.edu!jm36
From: jm36@hogtown.andrew.cmu.edu (John Gardiner Myers)
Newsgroups: comp.lang.perl
Subject: installing somewhere else (Re: 4.0 beta available)
Message-ID: <1991Mar7.002149.11409@cs.cmu.edu>
Date: 7 Mar 91 00:21:49 GMT
References: <1991Feb25.034137.10651@uvaarpa.Virginia.EDU>
Sender: netnews@cs.cmu.edu (USENET News Group Software)
Organization: Carnegie-Mellon University
Lines: 11

In article <1991Feb25.034137.10651@uvaarpa.Virginia.EDU> marc@mit.edu writes:
>It seems that the ``right'' solution is to have two configure
>variables, one for where the binaries/scripts/libraries should be
>installed, and one for where they should be read from.

This would be extremely helpful.  Here, we have to go through a
release cycle--things have to be installed in places like
/afs/andrew.cmu.edu/system/alpha/@sys/contributed/depot/perl/bin/perl
but appear in places like /usr/contributed/bin/perl.

I just modify the Makefile.