Re: Collations and Replication; Next Steps
От | Heikki Linnakangas |
---|---|
Тема | Re: Collations and Replication; Next Steps |
Дата | |
Msg-id | 541AE352.50202@vmware.com обсуждение исходный текст |
Ответ на | Re: Collations and Replication; Next Steps (Oleg Bartunov <obartunov@gmail.com>) |
Ответы |
Re: Collations and Replication; Next Steps
|
Список | pgsql-hackers |
On 09/18/2014 04:12 PM, Oleg Bartunov wrote: > On Thu, Sep 18, 2014 at 3:25 PM, Martijn van Oosterhout <kleptog@svana.org> > wrote: > >> On Thu, Sep 18, 2014 at 01:35:10PM +0900, Tatsuo Ishii wrote: >>> In my understanding PostgreSQL's manual MUST include the ICU license >>> term (this is not a problem). What I am not so sure is, any software >>> uses PostgreSQL also MUST include the ICU license or not. If yes, I >>> think this is surely a problem. >> >> Only if we're thinking of distributing it. If the user gets ICU from >> their distribution then there is no need to list the licence (just like >> we don't need to mention the licence of glibc). We only need link >> against it, not distribute it. > > I understand how it'd works with extension, but not with core. The same it works with libxml, openssl, libreadline and all the other libraries you can build with. - Heikki
В списке pgsql-hackers по дате отправления: