> Is it better in /contrib or gborg?
Gborg imho. I thought we were trying to move all non-core code there now. Isn't that why psqlodbc etc. were moved?
The argument was that it can be devopped and released independently?
Features in "contrib/" have a premium over external add-ons.
That is probably the average users perception. But I hope that is not the reason why dblink, dbmirror and the "rserv prototype" are under contrib/ while projects like erserver and slony1 live on gborg - just to take this class of projects as an example.
I totally agree that gborg is the right place for this, as it is for another few things that still are in contrib/ and don't belong there.
Jan
-- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] #
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
