+- On Friday (2/19/1999 12:39) Mate Wierdl <[EMAIL PROTECTED]> Wrote-
| On Thu, Feb 18, 1999 at 09:37:10PM +0000, Ralph Corderoy wrote:
| > The prefix can be specified when running configure; that sets the
| > definition in the Makefile. But when `make install' is done the
| > prefix can be over-ridden `make prefix=/tmp install'. This means software
| > gets built expecting to be in the default /usr/local but can actually be
| > installed somewhere else.
| >
| > If nmh supports this (I don't have the source to hand) then doesn't that
| > accomplish what you require?
|
| Not really, because what if I chose dirs during config which are not under
| prefix? Say, I have the binaries in $(prefix)/bin, but config files in
| /etc/nmh. Now, I would like to install all the compiled stuff under
| /tmp/nmh-root, say?
| --
| ---
| Mate Wierdl | Dept. of Math. Sciences | University of Memphis
|
%build
./configure --prefix=/usr/local --sysconfdir="\${prefix}/share/nmh"
make
%install
make prefix=${RPM_BUILD_ROOT}/usr/local install
If you wanted sysconfdir to be somewhere else, you just set it:
%install
make prefix=${RPM_BUILD_ROOT}/usr/local \
sysconfdir=${RPM_BUILD_ROOT}/etc/nmh install
I don't believe that there are any permutations of chasing and
installing in differnt places that the GNU coding standards won't
allow. nmh does a fine job of adhering to them too.
--
Stephen L. Ulmer [EMAIL PROTECTED]
Systems Programmer http://www.ulmer.org/
Northeast Regional Data Center VOX: (352) 392-2061
University of Florida FAX: (352) 392-9440
