> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 09 June 2000 11:59
> To: [EMAIL PROTECTED]
> Subject: [midgard] Re: Install problem: midgard php
>
>
> Alexander Bokovoy <[EMAIL PROTECTED]> writes:
>
> > There are Midgard RPMs for SuSE -- please look at
> www.midgard-project.org
>
> At the moment, I am working on a spec that will create a midgard RPM
> from the CVS sources that doesn't depend on or conflict with an already
> installed apache and its modules. So you can install a Midgard server
> without having to deinstall the stock apache.

Talk to me too on this.

I have rationalized the midhat 1.4b3 midgard spec file with the redhat 6.2
(late contrib) spec file where imap, ldap, postgresql and mysql are all php
loadable modules.

This went well (I'm new to midgard and don't want to drop back a few php
releases).

The amended .spec file is enclosed.  It uses php-3.0.16-config.patch (unix-y
patches to php3.ini-dist) also enclosed

I recommend these be used by redhat 6.2 users instead of the supplied .spec
file, it will produce a set of midgard-php packages remarkably similar to
the supplied php packages.  In line with redhat 6.2 midgard-php itself is
has prefix /usr, but there is no harm with midgard-lib and mod_midgard being
/usr/local I think?

I'll be glad to add 1.4b3 patches to the .spec file as they become
available.

In the end I will try and generate patches myself by diff-ing the cvs to the
current beta release (so other people can make the latest release).

But I don't see why anyone has to de-install the stock apache, unless it
does not support modules?

Final note: Any what patches have been made available for 1.4b3 ?

thanks

Sam

midgard-php.spec

php-3.0.16-config.patch

--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org

To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]

Reply via email to