Re: [GENERAL] pg_filedump binary for CentOS

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Boreham <david_list(at)boreham(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] pg_filedump binary for CentOS
Date: 2010-10-21 22:30:52
Message-ID: 201010212230.o9LMUqj07213@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Greg Stark wrote:
> On Thu, Oct 14, 2010 at 2:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> >> Should we consider moving pg_filedump into our /contrib?
> >
> > Can't: it's GPL.
> >
>
> I don't particularly see a problem with having GPL'd contrib modules.
> It would mean any users hoping to redistribute the package couldn't
> include those modules except under the GPL. But most repackagers don't
> include the contrib modules anyways. Even ones that do and want to
> include those modules would only have to include the source to that
> module.
>
> I can see not wanting to let that camel's nose in for fear of having
> packagers always be uncertain about the status of each contrib module
> though.

I think we should just link to the tool from our docs so there is no
license complexity. Where do we add it?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tim Uckun 2010-10-21 22:31:13 Re: Updates, deletes and inserts are very slow. What can I do make them bearable?
Previous Message Szymon Guz 2010-10-21 21:35:07 Re: COPY question

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-10-21 22:33:35 Re: Timeout and wait-forever in sync rep
Previous Message David E. Wheeler 2010-10-21 21:47:25 Re: UNION ALL has higher cost than inheritance