[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: define _prefix in *.spec
- From: Chris Adams <cmadams hiwaay net>
- To: rpm-list redhat com
- Subject: Re: define _prefix in *.spec
- Date: Wed, 16 Jan 2002 23:12:47 -0600
Once upon a time, Matthias Saou <matthias@rpmforge.net> said:
> Once upon a time, Chris wrote :
> > That depends: on my Tru64 based install, I'm installing _all_ RPMs under
> > /usr/local (to stay out of the way of the base OS and its packaging
> > system). Also, where there are command overlaps, I can choose which
> > command I get based on my PATH setting (PATH=/usr/local/bin:/usr/bin
> > gets GNU style stuff first, which PATH=/usr/bin:/usr/local/bin gets
> > Tru64 stuff first).
>
> I get your point :-) But still, maybe it would be worth the extra system
> configuration (ld, PATH...) to have rpms under yet another prefix? Simply
> to not mix programs installed from tarballs (which usually go under
> /usr/local) with the ones installed from rpms? Something like /usr/rpm with
> the "usual" subdirectories? Just a thought, since you may not be concerned
> at all if you don't install anything from tarballs ;-)
On Tru64, you can't change the default shared library search path. You
can set LD_LIBRARY_PATH (doesn't work for setuid binaries) or link
everything with -rpath (Compaq C) or -Wl,-rpath (GNU C), but both of
those options pretty much suck. You can also compile a full path into
each shared library (soname of /rpm/shlib/libncurses.so instead of
libncurses.so for example), but that would require a lot more work in
RPM building. Shared libraries are enough fun under Tru64 without this
(can't really have multiple versions of the same library around, so an
upgrade can require a lot of recompiles).
Also, I build RPMs of _everything_ now (even some nosrc ones for things
like Arkeia backup software). I'm going to create a separate directory
structure for local scripts, but everything else will either be in Tru64
setld or RPM format.
BTW: Does Red Hat have any kind of spec file "style" guide? I am
building most of my Tru64 RPMs by starting with the Red Hat Linux 7.2
(or 7.2 errata) SRPMs, and I'm running across a bunch of dumb stuff
(like a lot not using %{_prefix} or %{_bindir}). Also, a number of RH
spec files assume all the world is bash (so when /bin/sh is NOT bash,
the spec file doesn't work). I could open about 50 Bugzilla tickets on
this, but I don't know if I'd just be annoying someone... :-)
--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]