Hello Fred,
> I also didn't have the tenacity to go chugging around in the DB or
> backend code to figure out why, so I proceded to attempt an upgrade
> to 1.2.5. If you have Mandrake DO NOT install the Redhat RPMs on the
> Midgard site. In the arena of Apache, Mandrake differs radically.
> To be honest, installing newer Midgard on Mandrake is not a cup of
> tea, it requires alot of config tweaks on a compile. Mostly because
> Mandrake likes to store its conf files in /etc, the httpd and bins
> in /usr/sbin and the HTML in /home/httpd. There is no convienent
> /usr/local/apache. I am somewhat tempted to reinstall Apache in a
> new/original tree structure, but to be honest, I am now used to the
> way Mandrake thinks, and I like it, so I am sticking to it.
The structure of directories you've described is standard for
RedHat-based distributions and could be achived when compiling Apache
by selection layout RedHat (option --with-layout=RedHat to configure,
if memory serves me)
> In the mean time, Mandrake hasn't got a new set of RPM's going for
> Midgard yet, so if you have a problem with the install, let me know
> and I will do my best.
If you can, please download beta version of Midgard 1.2.6 from
www.midgard.f2s.com and try to create RPMs for Mandrake. I'm in
contact with Mandrake's developers but they aren't created RPMs yet,
mainly due license issues with MySQL (MandrakeSoft doesn't have
written permision to distribute non-GPLed version of MySQL which is
needed for Midgard) and the need of possible massive hacks to allow
Midgard to work with GPLed MySQL.
Best regards,
Alexander mailto:[EMAIL PROTECTED]
--
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]
