Re: contrib/pg_filedump - PostgreSQL File Dump Utility
| От | Barry Lind |
|---|---|
| Тема | Re: contrib/pg_filedump - PostgreSQL File Dump Utility |
| Дата | |
| Msg-id | 3C61E458.2090904@xythos.com обсуждение исходный текст |
| Ответ на | Re: contrib/pg_filedump - PostgreSQL File Dump Utility (Peter Eisentraut <peter_e@gmx.net>) |
| Ответы |
Re: contrib/pg_filedump - PostgreSQL File Dump Utility
Re: contrib/pg_filedump - PostgreSQL File Dump Utility |
| Список | pgsql-patches |
In following this thread, one question that was raised in my mind is what is the intended purpose of the contrib directory? I had thought that the purpose was as a place to put code that was experimental, or not stable enough to be in the main tree, but would someday when it matures get included into the main tree. Obviousely if there are different licenses this code couldn't ever be in the main tree. Is contrib then just a dumping ground of code related to the postgresql server (a kind of sourceforge for postgres)? I am sure the answer to that question is no. But then I really don't understand what should or should not be in contrib. thanks, --Barry Peter Eisentraut wrote: > Tom Lane writes: > > >>I do have concerns about including these six contrib modules in our >>distribution, however. It could be argued that the terms of the GPL >>forbid that. >> > > That is one thing. Another concern is that it confuses the general > public. People have certain expectations when it comes to PostgreSQL > code, and if every little subdirectory has its own license it just becomes > annoying. > >
В списке pgsql-patches по дате отправления: