On Wednesday 29 September 2004 07:45, Lanman wrote:
IMNSHO, It should be left on a development list somewhere until it it at least configurable. Further research on OGO has shown that the SOPE components won't compile on Mandrake 10.0, and without that you're left with several hours or days of work that don't accomplish a thing except to increase ones' frustration.
Now, having said all of that, you can count on someone flaming me for suggesting that OGO be left where it is until it's a tad more user-friendly, etc. Sigh! Here we go again!
For the record, I think that is a very sensible proposal for a package that seems to be difficult to install and configure.
I did do some checking into the packages on contrib as well as looking at some of the installation documents and came to much the same conclusion myself. oGo does not look like it is a suitable product for anyone that is not either familiar with the product already, or willing to put a lot of manual labor into getting it up and working.
Bryan,
I really hate it when you do that! Just when I thought I had found a challenging intellectual adversary, you go and agree with me on something! Damn! Where's Albert Einstein when ya need him? *Snicker*!
I suppose that now, you're gonna tell me that I can't bill you for the new keyboard, aren't ya? Grin! Good thing it's a tax write-off for me.
What I'm not "getting" from OGO, is the reasons why they felt it necessary to use a module (mod_ngobjweb.so) to handle the pages when most others use a web-page built using PHP. It just seems that they over complicated the construction of the suite. I suppose they had their reasons, but I'm not getting that quite yet. IMNSHO, it wasn't done in order to make the suite easier in most senses of the word, but perhaps it had something to do with an easier building of the suite.
Since OGO seems to be based on components from other groupware suites, it seems that they must have taken a turn somewhere that led them down a new path of construction, and this might be a factor. Most other ones I've looked at didn't give me SOPE hassles, and it wasn't necessary to build a module in order to get it working.
I'm assuming they must have had good reasons, but IMO, it would have been a lot better if they had setup a usable PHP-based admin page where you could do all the configs and see where your errors were. Some of the other suites already have that - ie; EGroupware. At least that way you can see your exact errors and eliminate them one at a time until it's all working.
But, Like I said,...that's just my opinion - for what it's worth.
Lanman Registered Linux User #190712
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
