Re: contrib vs. gborg/pgfoundry for replication solutions

Hello,<br /><br /> I believe that one problem with the contrib is that in order to build most of the contrib modules
youneed<br /> the PostgreSQL source. That is silly. If I have PostgreSQL installed with all headers, I should be able
to<br/> download a PostgreSQL project app (pgAdmin whatever) and just build it against PostgreSQL.<br /><br /> Very few
OSSprojects are like that. If I want PHP I don't need Apache source, I just need the Apache<br /> development stuff
(headersetc...).<br /><br /> If we were to break out contrib so it was on its own, let people figure out their own
buildmethods. You<br /> don't "have" to use autoconf (although it is a good idea). You don't NEED PostgreSQL source
etc...<br/><br /> Sincerely,<br /><br /> Joshua D. Drake<br /><br /><br /> Marc G. Fournier wrote:<br /><blockquote
cite="mid20040421232718.C32445@ganymede.hub.org"type="cite"><pre wrap="">On Wed, 21 Apr 2004, Rod Taylor wrote:
 
 </pre><blockquote type="cite"><pre wrap="">We have the current issue of people not knowing that projects like
pgadmin exist or where to find the jdbc drivers.   </pre></blockquote><pre wrap="">
Agreed ... but makign one big META package isn't going to fix that ... as
someone else suggested, put a README file in the contrib directory that
points ppl to projects.postgresql.org ...
 </pre><blockquote type="cite"><pre wrap="">These basic components (and others a large segment uses that are well
maintained) should go through a release cycle with the -core including
the platform test/report phase and be prominently listed in the
downloads area and documentation areas -- just as we do for PostgreSQL
proper.   </pre></blockquote><pre wrap="">
*ack* ... now the beta cycle just quadrupled in length ... so we develop
for 4 months, and beta for a year while we make sure everyone else's
packages work with the -core?

Most DBAs that I know will not upgrade based on a .0 release on a
production system ... they will wait for at least a .1 release ... between
.0 and .1 is when projects like PgAdmin should be doing their testing to
make sure that they are good for the new major release ...
 </pre><blockquote type="cite"><pre wrap="">Goto <a class="moz-txt-link-freetext"
href="http://postgresql.org">http://postgresql.org</a>,now track down the jdbc drivers or how to
 
use them. To a significant portion of our users this is more important
than CREATE FUNCTION is and in 7.5 jdbc documentation will be much more
difficult to find, but no less important than it used to be.   </pre></blockquote><pre wrap="">
Now, out of all of the PostgreSQL users, what % are using JDBC?  What %
are using ODBC?  What percentage of those using JDBC are also using ODBC?
What % of those using PgAdmin are also using ODBC?  For that matter, how
many ppl using JDBC only want to download the .jar file itself, and not
the source code?  % of Binary-Only PgAdmin users?  ODBC driver?

The point of projects.postgresql.org is that if someone *is* looking for
an addon, they should be pointed to projects.postgresql.org ... if you try
and merge everything into the -core distribution, you are either going to
miss something that *someone* wants to use at some point, *or* one helluva
large tar file to download ...

----
Marc G. Fournier           Hub.Org Networking Services (<a class="moz-txt-link-freetext"
href="http://www.hub.org">http://www.hub.org</a>)
Email: <a class="moz-txt-link-abbreviated" href="mailto:scrappy@hub.org">scrappy@hub.org</a>           Yahoo!: yscrappy
            ICQ: 7615664 </pre></blockquote><br /><br /><pre class="moz-signature" cols="72">-- 
 
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - <a class="moz-txt-link-abbreviated" href="mailto:jd@commandprompt.com">jd@commandprompt.com</a> - <a
class="moz-txt-link-freetext"href="http://www.commandprompt.com">http://www.commandprompt.com</a>
 
PostgreSQL Replicator -- production quality replication for PostgreSQL</pre>