| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | <obartunov(at)gmail(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, Peter Geoghegan <pg(at)heroku(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, <mkelly(at)tripadvisor(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, <mspilich(at)tripadvisor(dot)com> |
| Subject: | Re: Collations and Replication; Next Steps |
| Date: | 2014-09-18 13:51:14 |
| Message-ID: | 541AE352.50202@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)svana(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-09-18 13:57:26 | Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding) |
| Previous Message | Oleg Bartunov | 2014-09-18 13:12:52 | Re: Collations and Replication; Next Steps |