Re: Ding-dong, contrib is dead ...

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Ding-dong, contrib is dead ...
Date: 2006-09-05 19:31:42
Message-ID: 44FDD09E.2060108@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> "Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
>> I also agree with Andrew that pgfoundry is not a appropriate place for
>> userlocks. They should be properly documented with a cleaned up api.
>> I have no objection from them being removed from contrib in the short
>> term due to the gpl issue, although I am not sure how you can
>> copyright a function wrapper.
>
> Right, I see the pgfoundry project as just a backwards-compatibility
> thing for anyone who doesn't want to change their code. I'm happy to
> put some cleaned-up functions into core right now (ie, for 8.2) if
> someone will do the legwork to define and implement them.

hmm - that is all a nice and such - but is it really a good idea to do
this that late in the release-cycle ?
I think the most "natural" thing would be to replace the existing GPL'd
userlock code with the new one and discuss the API-change one for 8.3
and up ...

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew - Supernews 2006-09-05 19:31:51 Re: Ding-dong, contrib is dead ...
Previous Message Josh Berkus 2006-09-05 19:30:24 Re: Ding-dong, contrib is dead ...