Re: Policy on pulling in code from other projects?

On Fri, Jul 22, 2011 at 2:09 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> I am not neccessarily looking to include it in our tarball. What I asked
> was:
>
> 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?

Well, both ways are going to cause a certain number of problems.
Pulling it into the tree means we've got to maintain it forever;
requiring it via configure means that everyone who packages PostgreSQL
now has to include that library if they want to include PostgreSQL.

> I am not arguing one way or the other. I am trying to find the best
> solution. I personally think you are handwaving if you think we can build
> out a robust parser in a couple of hours.

I respect your opinion, but, in this case, I disagree.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company