So prbably the php modular version should be done the same way ? I mean with all the optional stuff you can have there ...
Ralf S. Engelschall wrote: > > In article <a2h5r3$2jpp$[EMAIL PROTECTED]> you wrote: >> Ralf S. Engelschall wrote: >>> In article <[EMAIL PROTECTED]> you wrote: >>> >>>> I don't quite seem to understand how options in spec files are supposed >>>> to work. rpm -i apache shows that this package CAN include ... how do I >>>> get it to include that stuff ? Where in the spec is it ? >>> >>> About which particular package are you talking? >> >> One example would be the apache package with the fastcgi option ... >> or the php module option ... > > Ah, I see. Yes, our "apache" package is a horribly example how complex a > .spec > can be if one really wants ultra-flexibility. But what do you expect from > an Apache package built by an ISP ;) > > The way to go is to use (assuming --prefix=/cw)... > > $ rpm -i apache-*.src.rpm > $ cd /cw/RPM/SRC/apache > $ vi apache.spec > [...switch options to "yes"...] > $ rpm -bb apache.spec > $ rpm -Uvh /cw/RPM/PKG/apache-*.rpm > > ...instead of the usual: > > $ rpm --rebuild apache-*.src.rpm > $ rpm -Uvh /cw/RPM/PKG/apache-*.rpm > > Ralf S. Engelschall > [EMAIL PROTECTED] > www.engelschall.com > ______________________________________________________________________ > The OpenPKG Project www.openpkg.org > Developer Communication List [EMAIL PROTECTED] ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
