|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
Question about gettext licensingHello All, I was concerned about gettext licensing. I was
able to build PostgreSql with gettext library. But this project is distributed
under GNU license. So I would like to know if we want to distribute product commercially
under different licenses, will it be okay ? If not then what approach usually companies,
which distribute PostgreSql as database, follow? Thanks & Regards, Vikram |
|
|
Re: Question about gettext licensingOn Tuesday 04 August 2009 01:35:36 Vikram Patil wrote:
> I was concerned about gettext licensing. I was able to build > PostgreSql with gettext library. But this project is distributed under > GNU license. > > So I would like to know if we want to distribute product commercially > under different licenses, will it be okay ? If not then what approach > usually companies, which distribute PostgreSql as database, follow? The gettext package contains the processing tools, but the run-time support is in your C library. So this is not different from compiling with GCC while the run-time support is again in the C library. -- Sent via pgsql-advocacy mailing list (pgsql-advocacy@...) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-advocacy |
|
|
Re: Question about gettext licensingOn Wed, Aug 05, 2009 at 10:56:47AM +0300, Peter Eisentraut wrote:
> On Tuesday 04 August 2009 01:35:36 Vikram Patil wrote: > > I was concerned about gettext licensing. I was able to build > > PostgreSql with gettext library. But this project is distributed > > under GNU license. > > > > So I would like to know if we want to distribute product > > commercially under different licenses, will it be okay ? If not > > then what approach usually companies, which distribute PostgreSql > > as database, follow? > > The gettext package contains the processing tools, but the run-time > support is in your C library. So this is not different from > compiling with GCC while the run-time support is again in the C > library. The library you really need to think about is libreadline, which is GPL, so if you ship a psql binary using it, your psql is also GPL. This may or may not concern you. If it does concern you, one alternative is to compile psql against libedit. Another is not include readline support in it at all. Cheers, David. -- David Fetter <david@...> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@... Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-advocacy mailing list (pgsql-advocacy@...) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-advocacy |
|
|
Re: Question about gettext licensingHey Peter,
I forgot to mention that I am trying to build on windows. So I am not using libreadline. Thanks for your valuable help. Thanks & Regards, Vikram -----Original Message----- From: Peter Eisentraut [mailto:peter_e@...] Sent: Wednesday, August 05, 2009 12:57 AM To: pgsql-advocacy@... Cc: Vikram Patil Subject: Re: [pgsql-advocacy] Question about gettext licensing On Tuesday 04 August 2009 01:35:36 Vikram Patil wrote: > I was concerned about gettext licensing. I was able to build > PostgreSql with gettext library. But this project is distributed under > GNU license. > > So I would like to know if we want to distribute product commercially > under different licenses, will it be okay ? If not then what approach > usually companies, which distribute PostgreSql as database, follow? The gettext package contains the processing tools, but the run-time support is in your C library. So this is not different from compiling with GCC while the run-time support is again in the C library. -- Sent via pgsql-advocacy mailing list (pgsql-advocacy@...) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-advocacy |
| Free embeddable forum powered by Nabble | Forum Help |