Re: [pgsql-advocacy] Increased company involvement
От | Magnus Hagander |
---|---|
Тема | Re: [pgsql-advocacy] Increased company involvement |
Дата | |
Msg-id | 6BCB9D8A16AC4241919521715F4D8BCE6C7428@algol.sollentuna.se обсуждение исходный текст |
Ответы |
Re: [pgsql-advocacy] Increased company involvement
|
Список | pgsql-hackers |
> >>>> What is being worked on right now is effectively reducing > >> things down > >>>> to: > >>>> > >>>> postgresql-server (including libpq) postgresql-<insert > add on here> > >>> > >>> So you mean to get an equivalent of > >> postgresql-8.0.2.tar.bz2, I will > >>> have to download 30+ tarballs? > >> > >> Or the WTKS one ... which will exist from day one, but not as > >> "integrated" > >> as Josh would like us to get to eventually ... > > > > I assume "as integrated as today", meaning I still only > need to do one > > "./configure" and one "make"? > > Correct, it may be something that someone can figure out how > to do easily (or, already knows how to do) though ... just > haven't had anyone step up to the plate on it, and don't > expect someone to until there is something for them to base > the work on. Ok. As long as I can do that (and as long as it's not named -WTKS- :P), I'm fine (since I'm basically not affected). And assuming that the standards applied to get into the wkts file is about the same as we have now for code quality etc. And as long as nothing is ripped until it actually works :) > > If not then it really takes away much of the point, doing "mget > > *.tar.gz" isn't that much harder than specifying a file.. > > If you seriously install *every* PL and every contrib file on > your server, then that is an option ... For PLs, usually I do. Then I activate them as they are needed. For contribs, no, I usually stick tsearch2 in there, but not many other contribs. //Magnus
В списке pgsql-hackers по дате отправления: