[Mimedefang] configure in wrong part of RPM spec file

[Kenneth Porter]

--On Tuesday, September 09, 2003 1:15 PM -0400 Kris Deugau
<kdeugau at webhart.net> wrote:

> Because "prep" in the context of rpm-building means "prepare to execute
> make".  For a somewhat more detailed "Why?", ask in linux.redhat.rpm, or
> redhat.rpm.general.  <g>

Reply on the RPM list (Jeff Johnson is the maintainer of RPM):

------------ Forwarded Message ------------
Date: Wednesday, September 10, 2003 7:55 AM -0400
From: James Olin Oden <joden at malachi.lee.k12.nc.us>
To: rpm-list at redhat.com
Subject: Re: configure in %prep or %build?

On Wed, 10 Sep 2003, Jeff Johnson wrote:

> Kenneth Porter wrote:
> 
> > Most of the RPM's I've encountered put configure in the %build section, but
> > the spec file for MIMEDefang puts it in the %prep section. Which is
> > "correct", and why? If there's a compelling reason to put it in %build,
> > I'll submit a patch to the MIMEDefang people.
> >  
> > 
> 
> There is no right or wrong.
> 
> Usually, configure is done in %build so that "rpmbuild -bp ..." gives
> a patched tree without side effects; running configure in %prep
> changes the tree more than one ususally wants.
> 
This of course makes it easier for someone to patch your software using
the SRPM.  If you put the configure in %prep, then of course they have
to untar the the tarball by hand.  If the SRPM already contained patches
then these need to be applied by hand.  In an rpm like RedHat's kernel
rpm putting "configure" in %prep would be a real pain.  In others 
its just an annoyance.
 
Cheers...james


_______________________________________________
Rpm-list mailing list
Rpm-list at redhat.com
https://www.redhat.com/mailman/listinfo/rpm-list


---------- End Forwarded Message ----------