Tony Maro wrote: > > So basically, the installation process for 1.4.2 is far from flawless. > > Had you asked you'd have been directed to our CVS versions, where most > > of these things were fixed. Besides that, if you do meet a situation > > like this, there's appearantly a few ways to deal with this: > > Well to be honest, I know nothing about using CVS. Never had the need > to use it. Do you download an RPM version of Midgard named "CVS"? > (just kidding, I have a general idea of what it is... but have always > stayed away from it.)
And to spare people the trouble of using CVS, we make daily snaps of CVS... even includes rpm packages, I think: http://nightlybuilds.midgard-project.org/ > > 1. Experiment (good) then complain to the authors (guess) > > 2. Experiment (good) then suggest ways for improvement (good, too many > > people think 1. is a informal way of 2. It isn't.) > > 3. Ask straight away (good). > > Personally I've always been of the try n try again then when all else > fails check the archives then finally ask once you have half of it > working. That's the way I learn best. You know, the whole "don't read > the directions until you realize the bicycle you're building will > probably have 30 left over pieces" mentality. Which makes you a perfect candidate for option #2. Suggestions for improvement don't always need to include patches. It also includes saying: this point of the INSTALL is unclear, because... > Being such a newbie, I don't consider myself progressed enough to write > a HOWTO. By the time I figure out how to get something to work I've > tried so much stuff I really have no idea what I did that finally make > it happen. I know that sentiment, and I maintain: those who consider themselves not progressed enough to write a howto are usually exactly the ones who are uniquely equipped to write it. Consider this: the HOWTO _I_ would write would be something along the lines of: 1. Install packages 2. Install database 3. Point your browser to... Notice a few steps missing? That's because they're second nature to me by now. I'm no longer qualified to write a HOWTO. Will new people need help, or even handholding, to write a HOWTO? Yes. But they'll spot the steps I'd miss, and help is available. > I think you're still going on the assumption that I was attacking you or > Midgard, both of which are incorrect assumptions. I apologize that you > read my original post that way. I acknowledge you did not mean it as an attack. Hardly anyone does. Yet the tone is one I've seen too many times before: starts out on a negative, and doesn't really progress into a positive[0], and that rubs me the wrong way. > I initially did not bore anyone with > details of how many times I compiled simply because I assume that > everyone else knew enough to not make the same mistakes I did. But were you to document them, or even let us know about it, we could prevent the next newby from making them. > You > proved that by mentioning the "./configure --help" statement above. I'm > sure you are the most noble of coders and the Midgard product the best > of breed. I only meant to express my own ineptness at making the > product work on my bastardized server and little knowledge. Understood. The intent was clear, I just wanted to express my thoughts about the form it was delivered in. If that, in turn, rubbed you the wrong way, you have my apologies. I can have a very short fuse at times. > Considering the current status of my system - stock Mandrake 8.1 Apache > and MySQL with a custom build of PHP using internal MySQL support -- http://cvs.midgard-project.org/midgard/php4/INSTALL, see at the end. This is a long-known problem with PHP that they see no need to document for, but _any_ PHP extension that uses MySQL or expat, except those two bundled with PHP themselves, will reliably conflict (like that term) with the bundled versions. They ship the bundled version to make it easier to build PHP4 with less external dependencies, but fail to take into account that some people _need_ those external dependencies. It's been reported and ignored. > Would you agree the best course of action is as follows:? > > 1) Un-install all of Midgard, RPM's and all Yes. > 2) Delete the MySQL database used by Midgard Not necesary. > 3) Recompile my PHP extensions but this time use the external MySQL > support compiled into it Right, same goes for expat if you use it in PHP. > I know it's not really your area, but could you refer me to a website > that will cover how to do #3 properly? I still have the sources > installed and could likely do a quick rebuild, if you call 2 hours on a > P2 400 quick, but don't know anything about external MySQL support. Fortunately, that's the easy part. Instead of doing --with-mysql, do --with-mysql=<path to libs and includes for mysql>. Same goes for --with-xml (or is it --with-expat these days?). > Will this required me to rebuild MySQL as well? Nope. > Or would you suggest > going ahead and compiling Midgard PHP module directly into the PHP as I > build it? Possible, but I don't generally recommend it. Easier to take upgrade Midgard with modules, and the performance loss is negligable. I haven't been able to measure the loss myself, but people tell me it's there, theoretically. Emile [0] It has now, BTW. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
