Re: State of RPMs - Mailing list pgsql-hackers

From teg@redhat.com (Trond Eivind Glomsrød)
Subject Re: State of RPMs
Date
Msg-id xuy4s5ely23.fsf@hoser.devel.redhat.com
Whole thread Raw
In response to State of RPMs  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
Lamar Owen <lamar.owen@wgcr.org> writes:

> > > Or, let's rephrase this in a positive way: Trond, where would be the
> > > best places to look for these newer features? I recall looking at other
> > > spec files to stumble across stuff that wasn't in the book.
>  
> > The doc directory of rpm and the macros file - 3.0.5 has been
> > released(with much stuff from 4.0-series) , 4.0 is due soon. After
> > that, the current plan is for the author to spend a couple of
> > hours/day creating more documentation.
> 
> That is _good_ news.  The doc directory had _some_ information -- but
> nothing on --buildpolicy.  Just a simple "--buildpolicy does this..."
> note in the man page, even, would be nice.

--buildpolicy is just a (now standard) macro:

./rpmpopt-4.0:rpm alias --buildpolicy --define '__os_install_post /usr/lib/rpm/brp-!#:+'

os_install_post is another macro, this is the second script:

[teg@hoser rpm]$ cat /usr/lib/rpm/brp-redhat 
#!/bin/sh

# These are the build root policies that Red Hat invokes at the end
# of the %install scriptlet.

# Compress man pages (Red Hat uses GNU gzip)
/usr/lib/rpm/brp-compress

# Strip ELF binaries (Red Hat uses GNU binutils).
/usr/lib/rpm/brp-strip

# Strip even more sections (Red Hat uses GNU binutils).
/usr/lib/rpm/brp-strip-comment-note
[teg@hoser rpm]$ 

> A new "Maximum RPM" would be nicer, though. (I am aware of the current
> project for the updation of Maximum RPM online....and I'm also aware
> that it really hasn't gone anywhere as of the last time I checked.)

If someone has time to contribute, that would be greeeat. I don't know
what parts of the documentation Jeff is planning to improve.

-- 
Trond Eivind Glomsrød
Red Hat, Inc.


pgsql-hackers by date:

Previous
From: Alex Pilosov
Date:
Subject: Re: INET/CIDR types
Next
From: Larry Rosenman
Date:
Subject: Re: INET/CIDR types