Hi Joerg, not touching the question whether or not intergating is a good idea, some comments.
> 2) The integration of the driver 'as is' into the OOo installation set > involes quite a lot of work, in detail > * manage a cws ( this should not be underestimated) I could offer help here. Managing CWS' is our daily work here in Hamburg :) > * integrate the postgresql code in the OOo build environment and > communicate to other porters (macosx, bsds, solaris sparc) to crosscheck > the cws This is an interesting issue, not to forget the legal stuff. We need to approve all 3rd-party code we integrate into OOo, and Legal sometimes is slow ... > * find out how to best plug the driver into OOo's installation routine. This should be a one-liner in some text file, if we're just talking about "install it every time OOo is installed". > * add a specialiced postgresql driver tab in the datasources dialog which would be the main advantage of an integration. We have plans for making the integration of third-party drivers more powerful, and give those drivers more control on their UI, but until this happens (and this could be whenever), integrating into regular builds is the only way to get a dedicated UI. > * future maintenance of the driver in OOo code base. The core team might in fact not be able to do this maintenance on the long term, at least for mere resource reasons, so this should not be underestimated. However, as long as *you* still work on this driver, it shouldn't make a difference into which CVS repository you check in your patches :) Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
