Re: inclusions WAS: Increased company involvement - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: inclusions WAS: Increased company involvement
Date
Msg-id 42784C1F.3070309@fastcrypt.com
Whole thread Raw
In response to Re: inclusions WAS: Increased company involvement  (Josh Berkus <josh@agliodbs.com>)
Responses Re: inclusions WAS: Increased company involvement
Re: inclusions WAS: Increased company involvement
List pgsql-hackers
<br /><br /> Josh Berkus wrote: <blockquote cite="mid200505031806.28560.josh@agliodbs.com" type="cite"><pre
wrap="">Dave,all:
 
 </pre><blockquote type="cite"><pre wrap="">This issue has come up before, and I opposed it then when the interfaces
were removed from the main tarball.
I really don't see the upside to reducing the size of the tarball at the
expense of ease of use.  Seems to me we are
bending over backwards to make it easy for people with dial up
connections to download our "enterprise class"
database.   </pre></blockquote><pre wrap="">
Small tarball size isn't the *primary* reason for having our 
"push-it-out-to-pgFoundry" attitude, it's the *tertiary* reason.  The main 
two reasons are:

1) If we start including everything that's "useful", where do we stop?  There 
are enough pg add-ins to fill a CD -- 200 projects on GBorg and pgFoundry and 
others elsewhere.  And some of them probably conflict with each other.  Any 
decision to include some projects and not others will alienate people and 
possibly be a mis-evaluation; the libpq++/libpqxx mistake comes to mind. </pre></blockquote> My main concern was
pushingout existing code, not adding code that was not in the tarball.<br /> I would have to agree deciding which to
includewould be onerous.<br /><blockquote cite="mid200505031806.28560.josh@agliodbs.com" type="cite"><pre wrap="">
 
2) As long as we're using CVS, the only way to organize autonomous project 
teams that have authority over their special areas but no ability to change 
central code is to "push out" projects to separate CVS trees. </pre></blockquote> This has never been an issue before,
AFAIK,nobody with commit privliges in a separate<br /> package has ever changed the code where they weren't supposed
to.<br/><br /> To sum this up; the arguments presented are:<br /><br /> 1) The tarball is/was  too big however nobody
evercomplained.<br /> 2) CVS does not allow different groups to have commit privliges, but nobody has ever violated the
trust<br/><br /> Is this really the situation ? <br /><br /><blockquote cite="mid200505031806.28560.josh@agliodbs.com"
type="cite"><prewrap="">
 
>From my perspective, putting together a coherent "distribution" of PostgreSQL 
with all the add-ins you want is the job of commercial distributors and 
possibly OSS projects like Bizgres. </pre></blockquote><br /><br /><pre class="moz-signature" cols="72">-- 
Dave Cramer
<a class="moz-txt-link-freetext" href="http://www.postgresintl.com">http://www.postgresintl.com</a>
519 939 0336
ICQ#14675561
</pre>

pgsql-hackers by date:

Previous
From: "John Hansen"
Date:
Subject: Re: A proper fix for the conversion-function problem
Next
From: Josh Berkus
Date:
Subject: Re: inclusions WAS: Increased company involvement