Re: next draft of rpm guidelines are here

[Gregory Leblanc <gleblanc cu-portland edu>]

CC'd directly, as well as to the list, which is perhaps what that first
line was requesting.  If not, oops, sorry.

On 05 May 2001 18:48:36 +0200, Spider wrote:
> (I'm in digest. so double reply)
> Actually, To use -both- preset CFLAGS and RPM_OPT_FLAGS is at best an 
> unclean solution and could quite possibly mess things up very much. I've 
> hit that problem a few times when repackaging a few broken rpm's that 
> did it that way. (good example:)
> CFLAGS="-Os -march=k6 -mcpu=k6" + RPM_OPT_FLAGS that are "-mcpu=i686 
> -march=i386" and some more on a default RedHat

Yeah, this seems like it wouldn't be at all good.  RPM provides ways for
packagers to set custom RPM_OPT_FLAGS.

> Another point in the default rpm macros taht joe random doe has is the 
> override in /usr/lib/rpm/<arch>/macros on a redhat, that aliases all x86 
> targets to i386 :/

Right, but I think (at least with rpm 4) you can do some magic with
/etc/rpm/<arch>/ in order to get custom macros defined.  I don't
remember the details, but I'll try to find them.

> the later issue about the optimizations as set in the default macros 
> could very well provide difficult, but I think the "cleanest" solution 
> would be something like :
> MY_FLAGS=`echo $CFLAGS | sed s/-fno-exceptions//`
> since that's something thats a bit more "restricted" to those packets 
> that actually use exceptions.

Ooooh, I've been trying to figure out how to do that for a couple of
days...  I think I'll hack this into my local gabber spec file.  

I suppose this brings up another topic...  There are a few "tips and
tricks" that we all have for doing packaging.  Some of these belong in
the packaging guidelines, but some of them don't.  We could probably put
something up on the GPP website for posting packaging tips and tricks.
Later,
    Greg

-- 
Troll, troll, troll your post
Gently down the feed
Merrily, merrily troll along
A life is what you need...