1 ?RCS: $Id: siteprefix.U,v 1.1 1999/07/08 18:32:57 doughera Exp doughera $
3 ?RCS: Copyright (c) 1999 Andy Dougherty
5 ?RCS: You may redistribute only under the terms of the Artistic Licence,
6 ?RCS: as specified in the README file that comes with the distribution.
7 ?RCS: You may reuse parts of this distribution only within the terms of
8 ?RCS: that same Artistic Licence; a copy of which may be found at the root
9 ?RCS: of the source tree for dist 3.0.
11 ?RCS: $Log: siteprefix.U,v $
12 ?RCS: Revision 1.1 1999/07/08 18:32:57 doughera
13 ?RCS: Initial revision
15 ?MAKE:siteprefix siteprefixexp +oldsiteprefix: Getfile Loc Oldconfig cat package prefix
16 ?MAKE: -pick add $@ %<
18 ?S: This variable holds the full absolute path of the directory below
19 ?S: which the user will install add-on packages.
20 ?S: See INSTALL for usage and examples.
23 ?S: This variable holds the full absolute path of the directory below
24 ?S: which the user will install add-on packages. Derived from siteprefix.
27 ?S: This variable is set non-null if the siteprefix was previously defined
28 ?S: and gets set to a new value. Used internally by Configure only.
30 : Set the siteprefix variables
33 After $package is installed, you may wish to install various
34 add-on modules and utilities. Typically, these add-ons will
35 be installed under $prefix with the rest
36 of this package. However, you may wish to install such add-ons
37 elsewhere under a different prefix.
39 If you do not wish to put everything under a single prefix, that's
40 ok. You will be prompted for the individual locations; this siteprefix
41 is only used to suggest the defaults.
43 The default should be fine for most people.
47 rp='Installation prefix to use for add-on modules and utilities?'
48 : XXX Here might be another good place for an installstyle setting.
51 *) dflt=$siteprefix ;;
54 : XXX Prefixit unit does not yet support siteprefix and vendorprefix
60 *) oldsiteprefix="$prefix";;
65 siteprefixexp="$ansexp"