On Wed, 2005-10-12 at 19:26 +1000, Neil Dugan wrote:
> I thought it would only be needed if you where distributing the source for
> Postgresql.
>
> Does the copyright get distributed with the binary Debian packages?
> I haven't been able to find it on my Linux box.
The copyright of all Debian
On Wed, Oct 12, 2005 at 07:26:48PM +1000, Neil Dugan wrote:
> I thought it would only be needed if you where distributing the source for
> Postgresql.
>
> Does the copyright get distributed with the binary Debian packages?
> I haven't been able to find it on my Linux box.
Yes it does, in all b
On Thursday 06 October 2005 08:34, Jim C. Nasby wrote:
> On Wed, Oct 05, 2005 at 04:14:03PM -0400, Andrew Sullivan wrote:
> > On Wed, Oct 05, 2005 at 09:49:06PM +1000, Neil Dugan wrote:
> > > If I was to develop a 'C' project that only used the libpg.so library
> > > and the rest was my own stuff w
On Wed, Oct 05, 2005 at 05:34:25PM -0500, Jim C. Nasby wrote:
> > Yes, because libpg.so is licensed under the BSD license. Note that
> > you can do this in a COPYRIGHT file. It just has to be "in all
> > copies", whatever that means.
>
> AFAIK, this would only apply if he was actually distributi
On Wed, Oct 05, 2005 at 04:14:03PM -0400, Andrew Sullivan wrote:
> On Wed, Oct 05, 2005 at 09:49:06PM +1000, Neil Dugan wrote:
> >
> > If I was to develop a 'C' project that only used the libpg.so library and
> > the
> > rest was my own stuff would I need to preserve the copyright to somehow?
>
On Wed, Oct 05, 2005 at 09:49:06PM +1000, Neil Dugan wrote:
>
> If I was to develop a 'C' project that only used the libpg.so library and the
> rest was my own stuff would I need to preserve the copyright to somehow?
Yes, because libpg.so is licensed under the BSD license. Note that
you can do
Neil Dugan wrote:
>If I was to develop a 'C' project that only used the libpg.so library and the
>rest was my own stuff would I need to preserve the copyright to somehow?
>I wouldn't be distributing any source at all just my executable and the
>library.
license preservation is relevant if you c
On Wednesday 05 October 2005 06:41, Aaron Glenn wrote:
> On 10/4/05, Welty, Richard <[EMAIL PROTECTED]> wrote:
> > Aaron Glenn wrote:
> > >Completely incorrect. You can do whatever you like with PostgreSQL;
> > >you just can't sue anyone when things go south.
> >
> > _and_ you need to preserve the
On 10/4/05, Welty, Richard <[EMAIL PROTECTED]> wrote:
> Aaron Glenn wrote:
> >Completely incorrect. You can do whatever you like with PostgreSQL;
> >you just can't sue anyone when things go south.
>
> _and_ you need to preserve the copyright notices.
excellent point.
---(e
Richmond Dyes wrote:
From my understanding of the license for Postgresql, there is no
licensing fees as long as you are not selling it yourself for a profit.
This is incorrect. Please see the other messages on this thread. The
product you are thinking of is MySQL.
Sincerely,
Joshua D. Drak
Aaron Glenn wrote:
>On 10/4/05, Richmond Dyes <[EMAIL PROTECTED]> wrote:
>> From my understanding of the license for Postgresql, there is no
>> licensing fees as long as you are not selling it yourself for a profit.
>Completely incorrect. You can do whatever you like with PostgreSQL;
>you just
On 10/4/05, Richmond Dyes <[EMAIL PROTECTED]> wrote:
> From my understanding of the license for Postgresql, there is no
> licensing fees as long as you are not selling it yourself for a profit.
Completely incorrect. You can do whatever you like with PostgreSQL;
you just can't sue anyone when thin
From my understanding of the license for Postgresql, there is no
licensing fees as long as you are not selling it yourself for a profit.
There are also free platforms to build your application on. I am myself
exploring the use of Centos with php, postgresql, apache with ssl
running as a secur
13 matches
Mail list logo
