blob: 421be97aec0ab9bf3473e32d7692fcada0fea200 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
?RCS: $Id: sitelib.U 167 2013-05-08 17:58:00Z rmanfredi $
?RCS:
?RCS: Copyright (c) 1996, Andy Dougherty
?RCS: Copyright (c) 1991-1997, 2004-2006, Raphael Manfredi
?RCS:
?RCS: You may redistribute only under the terms of the Artistic License,
?RCS: as specified in the README file that comes with the distribution.
?RCS: You may reuse parts of this distribution only within the terms of
?RCS: that same Artistic License; a copy of which may be found at the root
?RCS: of the source tree for dist 4.0.
?RCS:
?RCS: $Log: sitelib.U,v $
?RCS: Revision 3.0.1.1 1997/02/28 16:21:35 ram
?RCS: patch61: created
?RCS:
?MAKE:sitelib sitelibexp installsitelib: afs cat Getfile \
Oldconfig Prefixit test privlib package sed
?MAKE: -pick add $@ %<
?Y:TOP
?S:sitelib:
?S: This variable contains the eventual value of the SITELIB symbol,
?S: which is the name of the private library for this package. It may
?S: have a ~ on the front. It is up to the makefile to eventually create
?S: this directory while performing installation (with ~ substitution).
?S:.
?S:sitelibexp:
?S: This variable is the ~name expanded version of sitelib, so that you
?S: may use it directly in Makefiles or shell scripts.
?S:.
?S:installsitelib:
?S: This variable is really the same as sitelibexp but may differ on
?S: those systems using AFS. For extra portability, only this variable
?S: should be used in makefiles.
?S:.
?C:SITELIB:
?C: This symbol contains the name of the private library for this package.
?C: The library is private in the sense that it needn't be in anyone's
?C: execution path, but it should be accessible by the world. The program
?C: should be prepared to do ~ expansion.
?C: The standard distribution will put nothing in this directory.
?C: Individual sites may place their own extensions and modules in
?C: this directory.
?C:.
?C:SITELIB_EXP:
?C: This symbol contains the ~name expanded version of SITELIB, to be used
?C: in programs that are not prepared to deal with ~ expansion at run-time.
?C:.
?H:#define SITELIB "$sitelib" /**/
?H:#define SITELIB_EXP "$sitelibexp" /**/
?H:.
?T:prog
: determine where site specific libraries go.
set sitelib sitelib
eval $prefixit
case "$sitelib" in
'')
?X: remove any trailing -3.0 or other version indentification
prog=`echo $package | $sed 's/-*[0-9.]*$//'`
dflt="$privlib/site_$prog" ;;
*) dflt="$sitelib" ;;
esac
$cat <<EOM
The installation process will also create a directory for
site-specific extensions and modules. Some users find it convenient
to place all local files in this directory rather than in the main
distribution directory.
EOM
fn=d~+
rp='Pathname for the site-specific library files?'
. ./getfile
if $test "X$sitelibexp" != "X$ansexp"; then
installsitelib=''
fi
sitelib="$ans"
sitelibexp="$ansexp"
if $afs; then
$cat <<EOM
Since you are running AFS, I need to distinguish the directory in which
private files reside from the directory in which they are installed (and from
which they are presumably copied to the former directory by occult means).
EOM
case "$installsitelib" in
'') dflt=`echo $sitelibexp | sed 's#^/afs/#/afs/.#'`;;
*) dflt="$installsitelib";;
esac
fn=de~
rp='Where will private files be installed?'
. ./getfile
installsitelib="$ans"
else
installsitelib="$sitelibexp"
fi
|
