Policy on pulling in code from other projects?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Policy on pulling in code from other projects?
Date: 2011-07-21 17:43:06
Message-ID: 4E28652A.8050208@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


So I am looking intently on what it is going to take to get the URI
patch done for psql [1] and was digging around the web and have a URI
parser library. It is under the New BSD license and is strictly RFC RFC
3986 [2] compliant .

Now I have not dug into the code but the parser is used by other
projects. So question is:

Assuming the code actually makes this patch easier, do we:

A. Pull in the code into the main tree
B. Instead have it as a requirement via configure?


2. http://tools.ietf.org/html/rfc3986


Joshua D. Drake

Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579


Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-07-21 17:58:12 Re: fixing PQsetvalue()
Previous Message Simon Riggs 2011-07-21 17:30:25 Re: Re: [COMMITTERS] pgsql: Remove O(N^2) performance issue with multiple SAVEPOINTs.