Addressed to: [EMAIL PROTECTED]
"Michael J. McGillick" <[EMAIL PROTECTED]>
** Reply to note from "Michael J. McGillick" <[EMAIL PROTECTED]> Tue, 20
Jun 2000 22:34:26 -0400 (EDT)
>
>
> I'm sorry if I wasn't clear in my first message. Please let me
> explain what I'm trying to do.
>
> I went to the mod_ssl site, which was extremely helpful. I read
> through the example and it was very easy to build apache. I'm in the
> process of building a Red Hat 6.2 RPM with mst of the
> pre-configuration down, and then the end user will simply one one
> command to install, and then updtate the certificate section, make
> any personal modifications to the httpd.conf file, etc.
>
> I've got the entire spec file put together to do all three of the
> steps mentioned in the example doc on the web site, plus the
> directory structure is all in place, everything builds and installs
> and runs perfectly.
>
> I would like to include the php4 module already part of the RPM so
> when the user installs the RPM, they don;t have to go out and
> download php4, etc. They can simply add there php files to the html
> directory and away they go.
>
Is this a source/development RPM, or an end-user RPM? If the latter, I
think you just need to make sure it includes the src/modules/php4
directory, (after you build PHP4) and that the httpd.conf file includes
the AddType and possibly DirectoryIndex directives to activate PHP.
If it is a source/dev RPM, you've got me... I've never built an RPM,
the answer above is based on my understanding of what Apache needs.
Rick Widmer
Internet Marketing Specialists
http://www.developersdesk.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
