Re: contrib vs. gborg/pgfoundry for replication solutions
От | Bruce Momjian |
---|---|
Тема | Re: contrib vs. gborg/pgfoundry for replication solutions |
Дата | |
Msg-id | 200404220148.i3M1mCr07429@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: contrib vs. gborg/pgfoundry for replication solutions ("Magnus Hagander" <mha@sollentuna.net>) |
Ответы |
Re: contrib vs. gborg/pgfoundry for replication solutions
Re: contrib vs. gborg/pgfoundry for replication solutions |
Список | pgsql-hackers |
Magnus Hagander wrote: > > IMHO it's not all that important where the source is developed (core > cvs, gborg etc) - whichever suits the development/release model best > shuold be used (meaning inside core only if it should be released on the > very same schedule as the main backend only). > > What is more important is the exposure of the released versions. I think > it should be possible (and fairly easy) for projects developed outside > the core to get included in the "official download page", meaning go on > the ftp site and mirrors. Today it seems ODBC and pgadmin3 go there, but > pretty much nothing else (not even JDBC?). Perhaps a good structure > there would allow more proejcts to get that kind of exposure, and be > easier to find. > > I quite often get people who claim "there is no this or that" for pgsql > when it's on gborg - simply becauase they didn't find it on the ftp > site. If you go looking, you'll find it on gborg, but if you don't know > where to look it can be hard. Especially for newcomers. I was thinking about CPAN. They have download stuff, but it installs very easily. I wonder if we should allow gborg projects to interface to our configure output in a way that makes it easier for them to be installed. The gborg is easy for development and releasing, but loses in the easy-of-use category sometimes. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
В списке pgsql-hackers по дате отправления: