Re: Policy on pulling in code from other projects? - Mailing list pgsql-hackers

From Christopher Browne
Subject Re: Policy on pulling in code from other projects?
Date
Msg-id CAFNqd5Vdb5Gsi8NoY6fEpYyuhrBwgmmFjTAm0Pttx8b9KFocCw@mail.gmail.com
Whole thread Raw
In response to Re: Policy on pulling in code from other projects?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Policy on pulling in code from other projects?
List pgsql-hackers
<p>I generally agree, Josh, but I think readline is getting pointed at a bit too much.  Yeah, it's a bad one, but we
alsoinclude other stuff like zlib that doesn't commonly come up as an issue.<p>I'd argue something just a wee bit
different...<p>Bythe time we would add in:<p>- autoconf rules to detect it,<br /> - makefile rules to link it in<br />
-include file changes<br /> - wrappers to ensure use of pmalloc<br /> - Debian guys add build dependancies<br /> -  rpm
dependenciesget added<br /> - BSD ports dependencies<p>That is likely rather more code than 1 not terribly large file
ofC needed to do it ourselves.  And this code is rather worse, as it is in a bunch of languages, spread all over.<p>If
wewere gaining a lot of extra functionality "for free" it would be one thing.  That is true for libssl, and likely
zlib,but not here. 

pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON
Next
From: Greg Smith
Date:
Subject: Re: pgbench --unlogged-tables