Re: Policy on pulling in code from other projects?

On 21 July 2011 18:43, Joshua D. Drake <jd@commandprompt.com> wrote:
> 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?
>
> 1.
> http://archives.postgresql.org/message-id/1302114698.23164.17.camel@jd-desktop
>
> 2. http://tools.ietf.org/html/rfc3986

Without commenting on the practicalities of what you'd like to do,
including code from other projects in the tree is well precedented.
Off the top of my head, I can tell you that pgcrypto uses code from
various sources, while preserving the original copyright notices.

--
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services