Re: minor install issue (apache 1 sapi)

On Fri, Nov 14, 2003 at 06:19:16AM -0800, terry chay wrote: > Jani, > > Yes, this happens when I create an RPM, however this is still a bug. > Here is RPM's build process: > 1) read spec file and look in /usr/src/redhat/SOURCES for files > necessary to build RPM > 2) configure and compile with settings targeted at "/" > 3) make install into a temporary directory targetted at a temporary > directory > 4) if this succeeds, bundle sources and spec file into a source RPM > 5) bundle temporary directory and spec file into binary RPM > > First, it is perfectly valid that I create a php package against my > installed apache. In fact, this is how Red Hat does it themselves and > the only valid way to safely replace an RPM with a non-distribution one > (this is why you should normally compile into /opt or /usr/local). The > reason Fedora hasn't found this bug has to do with the fact that the > later versions of Red Hat (since 9.0?) link against Apache 2 which > doesn't have this bug. This does affect the SAPIs for 2.0 too - we've historically patched that out the unsubtle way, e.g.: - if test -z $APXS -q SYSCONFDIR; then + if true; then INSTALL_IT="\$(mkinstalldirs) '$APXS_LIBEXECDIR' && \ ... > P.S. The Fedora PHP RPM is an absolute mess. It applies 12 patches and > separately compiles the cgi/sapi modules even though PHP has long since > built out both when you compile the SAPI. I don't know if there is > anything interesting in there, but you can download it from them and > apply "rpm2cpio <sourcetarball> | cpio -ivmud" and rummage around at > the patches. You can also see many of the patches by checking the archives for this list, and the cvs archives where they get checked in :) Regards, joe