Re: define _prefix in *.spec

[Chris Adams <cmadams hiwaay net>]

Once upon a time, Tim Mooney <mooney@dogbert.cc.ndsu.NoDak.edu> said:
> Why do you say you can't have multiple versions of shared libraries
> around?  There are at least two ways to do it: the classic
> BSD/Solaris/Linux way of just having the version in the soname & file
> name, and the OSF way, of embedding the version in the internal version
> field and then keeping older versions in their own subdirectory, named
> for whatever version they have.

Well, okay, yes you can have them.  But most (every?) package by default
that supports shared libraries on Tru64 names them libblah.so.  I'm not
sure how to change that to something like libblah.so-1.2.3 or
libblah-1.2.3.so (and still make the linker find it when someone does
-lblah).  If I put the old version of libblah.so in a subdirectory, how
would /sbin/loader (the dynamic linker) find it for binaries that need
the old version?

> >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... :-)
> 
> Be polite and gentle when you do, and be prepared for a few people that will
> say "who cares if it doesn't work on some non-Linux platform".

:-)

I've been thinking on a basic "form" letter that tries to be as nice as
possible.

Some of the RH RPMs even have things like "%ifos linux" for some things
(and those packages work out of the box or with patches added that are
Tru64 specific).  I don't plan on submitting anything that is Tru64
specific, but for things in the RPMs that make it difficult to port to
other platforms, I'll try to politely suggest a change (and ignore any
flames :-) ).

> I've definitely picked up tips and tricks from some of the Red Hat rpms
> I've seen, but overall there are some things I haven't liked about them
> in the past, so I've basically just developed my own style that works well
> for our site.  Building for multiple platforms and OSes from one spec file
> tends to mean that you have to do things a little differently in some
> cases anyway.
> 
> Tim
> -- 
> Tim Mooney                              mooney@dogbert.cc.ndsu.NoDak.edu
> Information Technology Services         (701) 231-1076 (Voice)
> Room 242-J6, IACC Building              (701) 231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
> 
> 
> 
> _______________________________________________
> Rpm-list mailing list
> Rpm-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/rpm-list

-- 
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.