Re: [OT] MySQL is bad, but THIS bad? - Mailing list pgsql-hackers

From Dawid Kuroczko
Subject Re: [OT] MySQL is bad, but THIS bad?
Date
Msg-id 758d5e7f0605200529s21bc6b4aye428e35977bd6d04@mail.gmail.com
Whole thread Raw
In response to Re: [OT] MySQL is bad, but THIS bad?  (Lukas Smith <smith@pooteeweet.org>)
Responses Re: [OT] MySQL is bad, but THIS bad?
Re: [pgsql-advocacy] [OT] MySQL is bad, but THIS bad?
List pgsql-hackers
On 5/20/06, Lukas Smith <smith@pooteeweet.org> wrote:
> The improvements to the installer are great, but there simply needs to
> be a packaged solution that adds more of the things people are very
> likely to use. From my understanding Bizgres goes in that direction? I
> just think that whatever highly packaged solution PostgreSQL picks, this
> should be the download that is pushed at conferences, in articles and
> books. People with a clue will still know where they can get the clean base.

Hmm, a Comprehensive PostgreSQL Archive Network? ;)

I mean, something like CPAN, CTAN or CRAN? :)

I mean, the -contrib is great, but pushing other things there is a bit
tricky (to say the least) from the maintenance point of view.  (Every
bugfix, a new release of -contrib, etc, etc...).

Then again PGfoundry is great to keep development centered, but
finding and building a new package is not really a one-liner, and
if you're unlucky you might get alpha-quality code installed. :)

I think a CPgAN-like solution would be the best.  A uniform method
of getting approved Pg extensions.  It would simplify installing the
extensions, and would encourage distributions to package such
extensions.  Somebody suggested apt-get install postgresql-contrib.
Imagine:
apt-get install postgresql-datatype-fqdn
apt-get install postgresql-gist-ltree
...and so on.

Regards,
     Dawid

pgsql-hackers by date:

Previous
From: "Mark Woodward"
Date:
Subject: Re: String Similarity
Next
From: "Mark Woodward"
Date:
Subject: Re: String Similarity