From: Robert G. B. <rg...@ph...> - 2000-12-31 01:40:46
|
On Sat, 30 Dec 2000, Jarl Friis wrote: > On Fri, 29 Dec 2000, David Paschal wrote: > > > Hi, Jarl. > > > > Yes, it might be more appropriate to put daemons such as ptal-printd in > > ${prefix}/sbin, particularly as I add more daemons. I'll take a look at > > your attachments later because I can't seem to decode them with the mail > > client I'm using at the moment (not your fault). <deleted> > > Timothy Lee has been working on a RedHat SRPM, so you might want to > > coordinate your efforts with his. I would greatly prefer to post one > > .src.rpm file that works on all RPM-based distributions, but of course > > reality may dictate otherwise. :-) > > from what I can see RPM is not designed for that feature, in the SPEC file > part of the src.rpm you specify where to put files, i.e. SuSE put libs in > /usr/lib/ wheras RedHat puts them in /usr/local/lib Actually, RH puts everything in /usr and nothing at all in /usr/local. It is also straightforward to build a relocatable RPM if nothing in it needs an absolute path. The only tricky part that I can see of an RPM is deciding where to put the kernel modules, which generally need to be built "just" for the kernel they are intended to run under. For the daemon this won't matter, and I agree that it should go in /usr/sbin and not /usr/bin. Or more practically, in ${prefix}/sbin. If anybody needs/wants it, I can contribute a matching "generic template" specfile and Makefile that do a gangbusters job of building rpm's in userspace. That is, everything is done by make targets -- make tgz builds a spec-ready or build-ready whatever.tgz and make rpm builds a very nice rpm, all automagically, with version/release numbers defined only in the Makefile. rgb -- Robert G. Brown http://www.phy.duke.edu/~rgb/ Duke University Dept. of Physics, Box 90305 Durham, N.C. 27708-0305 Phone: 1-919-660-2567 Fax: 919-660-2525 email:rg...@ph... |