Tom,
On re-reading the thread, I'm more than a bit confused by this response.
I thought you were suggesting that the top-level configure should have
a simple option that says please build and install all the contrib
modules while you are at it. Right now that requires a separate step
cd
On Thu, 12 May 2005 02:44 pm, Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
First, I *really* wish we'd call it something else. Contrib conveys
unsupported to people.
[snip]
Which is as it should be, I think. Contrib is essentially the not
quite
Russell Smith [EMAIL PROTECTED] writes:
I suppose the question is, at what point are contrib modules
re-reviewed for inclusion into core? And if they are continuing not
to make it, is there something else that should be done with them?
Basically, if someone wants a contrib module in core,
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
First, I *really* wish we'd call it something else. Contrib conveys
unsupported to people.
And that's exactly what it is supposed to mean. We say, these modules
do not necessarily meet our
Marc G. Fournier wrote:
... but stuff like admintools should be on pgfoundry ...
This is a quite *ix centric attitude. Please note that probably 90 % of
win32 installations have them installed by default (from the win32
installer). People moving to Linux because they need better performance
On Thu, 12 May 2005, Andreas Pflug wrote:
Marc G. Fournier wrote:
... but stuff like admintools should be on pgfoundry ...
This is a quite *ix centric attitude. Please note that probably 90 % of
win32 installations have them installed by default (from the win32
installer). People moving to Linux
Marc G. Fournier wrote:
'k, now i'm confused ... what are you looking at here, in contrib, as
being 'admintools'? Right now, anything in contrib is 'add-on' anyway,
so they'd still be as confused, I'd think ...
Well at least it would be contained in the full tarball, not coming from
a 3rd site
Andrew,
* Move some things from /contrib into main tree
* Move some /contrib modules out to their own project sites
A contrib shuffle is on my personal TODO list. Look for a list in a couple
weeks.
--
Josh Berkus
Aglio Database Solutions
San Francisco
./configure --with-perl --with-dblink --with-newsysviews
This would make installing and upgrading BSD ports easier.
David
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
Folks,
Hey, I can see a way for /contrib to become a lot better option for
stuff-we're-not-sure-whether-to-include.
What if we could build contrib modules through a build-time switch for
PostgreSQL? Like,
./configure --with-perl --with-dblink --with-newsysviews
This would seem a *lot*
Josh Berkus wrote:
Folks,
Hey, I can see a way for /contrib to become a lot better option for
stuff-we're-not-sure-whether-to-include.
What if we could build contrib modules through a build-time switch for
PostgreSQL? Like,
./configure --with-perl --with-dblink --with-newsysviews
This
On Wed, May 11, 2005 at 02:34:21PM -0700, Joshua D. Drake wrote:
I could see --with-contrib but other than that... there are ALOT of
packages in contrib.
I'm not configure expert, but I think it wouldn't be hard to do
something like --with-contrib='module1 module2 module3'. I believe
there's
Josh Berkus wrote:
Folks,
Hey, I can see a way for /contrib to become a lot better option for
stuff-we're-not-sure-whether-to-include.
First, I *really* wish we'd call it something else. Contrib conveys
unsupported to people. Maybe we should call it modules or something
like that.
What if
Andrew,
First, I *really* wish we'd call it something else. Contrib conveys
unsupported to people. Maybe we should call it modules or something
like that.
Agreed.
I honestly don't see that it buys a lot. (and the technical obstacle is
that there's a maintenance cost, if nothing else).
It
Jim C. Nasby wrote:
On Wed, May 11, 2005 at 02:34:21PM -0700, Joshua D. Drake wrote:
I could see --with-contrib but other than that... there are ALOT of
packages in contrib.
I'm not configure expert, but I think it wouldn't be hard to do
something like --with-contrib='module1 module2 module3'. I
On Wed, May 11, 2005 at 02:55:46PM -0700, Josh Berkus wrote:
First, I *really* wish we'd call it something else. Contrib conveys
unsupported to people. Maybe we should call it modules or something
like that.
Agreed.
Ditto
I honestly don't see that it buys a lot. (and the technical
Andrew Dunstan [EMAIL PROTECTED] writes:
Josh Berkus wrote:
What if we could build contrib modules through a build-time switch for
PostgreSQL? Like,
I honestly don't see that it buys a lot. (and the technical obstacle is
that there's a maintenance cost, if nothing else).
I'm with Andrew
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Josh Berkus wrote:
What if we could build contrib modules through a build-time switch for
PostgreSQL? Like,
I honestly don't see that it buys a lot. (and the technical obstacle is
that there's a maintenance cost, if
Andrew Dunstan wrote:
First, I *really* wish we'd call it something else. Contrib conveys
unsupported to people.
And that's exactly what it is supposed to mean. We say, these modules
do not necessarily meet our standards with regard to code quality,
portability, user interfaces,
Josh Berkus wrote:
What if we could build contrib modules through a build-time switch
for PostgreSQL? Like,
./configure --with-perl --with-dblink --with-newsysviews
This would seem a *lot* more user friendly to me, and easier on the
package builders. What's the technical obstacle to it?
Peter,
I don't see how this makes it any more user friendly or easier on
package builders. Is your aim to make building contrib more accessible
or building only specific contrib modules more accessible?
Building specific contrib modules.
--
--Josh
Josh Berkus
Aglio Database Solutions
San
Josh Berkus josh@agliodbs.com writes:
Peter,
I don't see how this makes it any more user friendly or easier on
package builders. Is your aim to make building contrib more accessible
or building only specific contrib modules more accessible?
Building specific contrib modules.
On re-reading
Peter Eisentraut [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
First, I *really* wish we'd call it something else. Contrib conveys
unsupported to people.
And that's exactly what it is supposed to mean. We say, these modules
do not necessarily meet our standards with regard to code
23 matches
Mail list logo
