Re: modules

From: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
To: Aidan Van Dyk <aidan(at)highrise(dot)ca>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: modules
Date: 2008-04-03 16:21:29
Message-ID: 47F50409.8040205@cheapcomplexdevices.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Aidan Van Dyk wrote:
> * Greg Sabino Mullane <greg(at)turnstep(dot)com> [080403 09:54]:
>> I emphatically do NOT mean
>> move to pgfoundry, which is pretty much a kiss of death.
>
> But that begs the question of *why* it's a kiss of death?

> For instance, in "perl land", having something in "CPAN" and not in
> "perl core" is most certainly *not* a kiss of death? Why is it so
> different for PostgreSQL?
> Is it because the infrastructure behind CPAN is much better than that
> behind pgfoundry?

I wouldn't say one is better than the other. PGFoundry and CPAN have
totally disjoint feature sets. PgFoundry's like SoruceForge +
Bugtrackers + Discussion Forums + Surveys + Mailing Lists -- pretty
much everything except installable packages.

CPAN and RubyGems is very much focused on installable packages.

> Or is it because CPAN is better "vetted" and "organized" than pgfoundry?
>
> Or is it because the projects that go into CPAN are better quality and
> projects in pgroundry?

To simplify those two:
CPAN contains installers that mostly "just work".
PGFoundry contains mostly works-in-progress without installers.

In response to

  • Re: modules at 2008-04-03 14:01:38 from Aidan Van Dyk

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2008-04-03 16:22:14 Re: modules
Previous Message Tom Dunstan 2008-04-03 16:15:52 Re: modules

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2008-04-03 16:22:14 Re: modules
Previous Message Tom Dunstan 2008-04-03 16:15:52 Re: modules