From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | mlw <pgsql(at)mohawksoft(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: contrib and licensing |
Date: | 2003-04-02 22:22:05 |
Message-ID: | Pine.LNX.4.33.0304021520390.17953-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2 Apr 2003, mlw wrote:
>
>
> Tom Lane wrote:
>
> >mlw <pgsql(at)mohawksoft(dot)com> writes:
> >
> >
> >>I know nothing in contrib should be GPL, I have no problem with that.
> >>The question is the requirement of a GPL library to build a contrib project.
> >>
> >>
> >
> >
> >
> >>My SOAP/XML function will probably require my LGPL library as there is a
> >>lot of code I have written that I would need to implement it.
> >>
> >>
> >
> >If it won't work without your library then there's not much point in
> >putting it into contrib. Might as well just put it in your library
> >and distribute same as you have been doing.
> >
> >
> I'm a little put off by this attitude, are you saying there are no LGPL
> dependencies in PostgreSQL or /contrib?
>
> If that is a real objective, I'm surprised.
I think it's more that if the lib is commonly included in most
environments, like say readline is, then someone will have to download the
lib seperately anyway, so you might as well have the soap functions be
there at the same place.
If your LGPL lib and / or an analog in BSD land are common, then including
it in contrib would make perfect sense.
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2003-04-02 22:25:41 | Re: contrib and licensing |
Previous Message | mlw | 2003-04-02 22:16:03 | Re: contrib and licensing |