From xemacs-m  Wed Aug 27 08:32:30 1997
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id IAA01911
	for <xemacs-beta@xemacs.org>; Wed, 27 Aug 1997 08:32:29 -0500 (CDT)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.8.7/8.8.7) with ESMTP id JAA18266
	for <xemacs-beta@xemacs.org>; Wed, 27 Aug 1997 09:32:28 -0400
Message-Id: <199708271332.JAA18266@black-ice.cc.vt.edu>
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: package-path questions 
In-Reply-To: Your message of "Wed, 27 Aug 1997 09:54:32 +0300."
             <199708270654.JAA07476@merlin.ornet.co.il> 
From: Valdis.Kletnieks@vt.edu
X-Url: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <199708191252.OAA05406@metheny.enst.fr> <ocroh6ub4s0.fsf@ml.com> <199708261546.SAA04960@merlin.ornet.co.il> <86g1rxnde6.fsf@kramer.in.aventail.com>
            <199708270654.JAA07476@merlin.ornet.co.il>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1801396812P";
	micalg=pgp-md5; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 27 Aug 1997 09:32:27 -0400

--==_Exmh_-1801396812P
Content-Type: text/plain; charset=us-ascii

Ricardo Marke (?did I mangle the attrib?) writes:
> >>>>> William M Perry writes:
 
>  William:   Well, actually, it would be better if we adopted something like Perl's
>  William: Makefile.PL strategy.  Then you would just do:
> 
>  William: xemacs -batch -l Makefile.el -eval '(make-makefile)'
>  William: make install
> 
>  William:   Makefile.el would set up a hash table of 'normal' targets that most
>  William: people would want to make, and then make-makefile would substitute
>  William: package-dir and friends at appropriate places.
> 
>  William: -Bill P.
> 
> Yes, Yes, Yes, in this way, you will get the correct location of the
> different directories, by using the allready well known locations.

Just  as an aside - in  some situations, the  install directory is NOT
the run directory.   For instance, this  is  true if you're  using the
Depot package  to manage /usr/local, or if  you're using AFS (where in
some configs, /usr/local is read-only, and to  write on it you need to
use a  different  pathname).  If you  implement this   sort of scheme,
please make sure  to not screw this up.  The base XEmacs package is an
exemplary good citizen about this, since  it can find itself no matter
WHERE it  was installed.  Most GNU  toools and some other packages are
fairly easy to get to work, requiring only a:

make prefix=/usr/local     # to build
make install prefix=/staging/area   # to stage
<mumble>		# magic (depot/AFS) to move to production

A good example of how NOT  to do it  is gcc, which requires some major
Makefile hacking to prevent it from re-compiling the new 'prefix' into
the binary when you say 'make install'.  Blech.  ;)

OK.. I'll quit ranting now. ;)

-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech



--==_Exmh_-1801396812P
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

iQCVAwUBNAQsatQBOOoptg9JAQHE8gP+OBlRSFEldT8PlwGTV+5swqcmdiMzefIg
8C6Cmq4x4YbBZkwDyUWvW87QXF/d7kIoCjA1BdQo+QpuerkQ4FPBk7SbgXKIxNDj
+rZ/MM2Ld5juPohqmB4To+5V4/OYS2wxoppbV08HIOAObeuwF7GVyrMW3jI2bOnZ
jssyXuuJTz8=
=dITY
-----END PGP MESSAGE-----

--==_Exmh_-1801396812P--

