Re: [pgsql-advocacy] Increased company involvement
От | Robert Treat |
---|---|
Тема | Re: [pgsql-advocacy] Increased company involvement |
Дата | |
Msg-id | 1115140141.24440.5.camel@camel обсуждение исходный текст |
Ответ на | Re: [pgsql-advocacy] Increased company involvement (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: [pgsql-advocacy] Increased company involvement
Re: [pgsql-advocacy] Increased company involvement |
Список | pgsql-hackers |
On Tue, 2005-05-03 at 12:40, Peter Eisentraut wrote: > Joshua D. Drake wrote: > > Not really that ugly. It is just an extra compile step. Besides > > you don't have to package it just because it is in the Tarball. > > Since you keep raising that point: Not packaging something is not a > valid solution to something being hard to package. > Is telling the rpm maintainers to go fix their rpm's an option? As has been hashed out before, the only thing that makes plphp different from other pl's is that some of the current packagers are taking shortcuts with the packaging scripts which introduces dependency issues. IMHO what is included in the postgresql cvs and what is included in the main tarball for postgresql should not be dictated by outside packagers. Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
В списке pgsql-hackers по дате отправления: