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
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Vivek Khera
> Sent: Thursday, October 06, 2005 1:55 PM
> To: Postgres General
> Subject: Re: [GENERAL] License question
>
>
> On Oct 4, 2005, at 4:38 PM,
On Oct 4, 2005, at 4:38 PM, Aaron Smith wrote:
I never imagined that I would get so many responses. Thanks for all
the great information!
depending on the nature of your DB you may wish to investigate SQLite
as well. it is designed to be embedded into apps, not run as a
separate server,
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
I had thought we were completely sunk until we moved everything over
to .Net.
Insert microsoft wisecrack of your choice here : )
---(end of broadcast)---
TIP 6: explain analyze is your friend
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
I never imagined that I would get so many responses. Thanks for all the
great information! This really cleared it up for us. It looks like I
will take a good long look at postgresql and see how well I can make it
interface into our product. This was extremely good news for me... I had
thought w
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
> This brings me here. I have heard of PostGreSQL, so it's not
> new to me.
> But all this licensing is. And maybe you can help get some
> clarification for the MySQL licensing too.
>
> We will not be selling the database software. We may install
> it for them, though. In fact, most of the t
Also sprach Aaron Smith ([EMAIL PROTECTED])
[License questions]
PostgreSQL is released under BSD License. This license say (informal,
IANAL) Do whatever you want with the code, but keep the author's
acknowledgements.
BSD licensed software is quite often incorporated into commercial
products, li
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
Hi,
>You can close source it, you can sell it, you can rename it.
Add to that: As long as you leave the copyrights notices alone...
Isn't that what the BSD license is particularly about? [but then, I
might be wrong there]
Regards,
Arthur
---(end of broadcast)-
On Tue, 2005-10-04 at 09:49, Aaron Smith wrote:
SNIP
> We will not be selling the database software. We may install it for
> them, though. In fact, most of the time, we will be the ones to install
> it, and we charge for that time. Our customers are very aware that we
> did not write it, nor a
[snip]
> Knowing all this, what do we need to purchase, what can we do and what
> can't we do? It's hard getting a straight answer from anyone that is
why
> I am here. If we can't do it, we won't. If we can save our customers
> some money while getting them really good options and software, we
woul
Joshua D. Drake wrote:
This brings me here. I have heard of PostGreSQL, so it’s not new to me.
But all this licensing is. And maybe you can help get some clarification
for the MySQL licensing too.
You can do anything you want with PostgreSQL. You can close source it,
you c
Hi,
If I'm not wrong, Postgres comes with a BSD license, which means that
it (literally) doesn't matter what you do with the sources or how you
link your applications to the Postgres libraries. Pervasive goes into
details here: http://www.pervasivepostgres.com/postgresql/mysql.asp.
Regards,
Ar
> This brings me here. I have heard of PostGreSQL, so it’s not new to me.
> But all this licensing is. And maybe you can help get some clarification
> for the MySQL licensing too.
>
You can do anything you want with PostgreSQL. You can close source it,
you can sell it, you can rename it.
You
25 matches
Mail list logo
