On Thu, 5 May 2005, Dave Cramer wrote:
> pl-j and pl/java are working together to create a shared interface so
> that they can co-exist. This is the part that we wish to have added to
> the main source tree. It will just be the C portion of the code that
> does rely on the backend.
Note that what Tom is proposing is actually yanking *all* PLs from the
core source tree, but having them all within the core CVS ... I believe
his "motivation" is that he only has one CVSROOT to set to get at all the
files, but that they are seperate from the core distribution itself ...
Basically, each has to be buildable/distributable standalone, but easily
accessible for making changes if/when APIs change ...
Tom, am I understanding correctly?
>
> Dave >
> Tom Lane wrote:
>
>> "Joshua D. Drake" <jd@commandprompt.com> writes:
>>
>>> Kind of offtopic but at that point should we also include plJava?
>>>
>>
>> Not decided, but it's surely on the radar screen for this discussion.
>> Joe Conway's PL/R is in the back of my mind as well --- it likely has
>> a smaller userbase than the first two, but from a maintenance standpoint
>> it probably belongs on the same level.
>>
>>
>>> Should we put plPHP in contrib/plphp? With its own build options?
>>>
>>
>> Not under contrib either: it's got to be a separate source tree.
>> I grow a bit weary and am not seeing exactly how this maps to a CVS
>> setup... do we need more than one CVS module?
>>
>> regards, tom lane
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 2: you can get off all lists at once with the unregister command
>> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>>
>>
>>
>
> --
> Dave Cramer
> http://www.postgresintl.com
> 519 939 0336
> ICQ#14675561
>
>
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664