Re: Collations and Replication; Next Steps - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Collations and Replication; Next Steps
Date
Msg-id 20140918.133510.1965988019461736313.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: Collations and Replication; Next Steps  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Collations and Replication; Next Steps  (Peter Geoghegan <pg@heroku.com>)
Re: Collations and Replication; Next Steps  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
> On Wed, Sep 17, 2014 at 9:06 PM, Oleg Bartunov <obartunov@gmail.com> wrote:
>> We use ICU with postgres for many years in our  mchar extension, which
>> provides  case-insensitive  text data type for popular  russian financial
>> system.  I don't know if we may ask ICU to give us special BSD-compatible
>> license ?
> 
> I don't think that's necessary. Firebird uses ICU, and has similar
> licensing terms to PostgreSQL.

http://source.icu-project.org/repos/icu/icu/trunk/license.html

........permission notice appear in supporting documentation.Permission ishereby granted, free of charge, to any person
obtaininga copy ofthis software and associated documentation files (the "Software"), todeal in the Software without
restriction,including withoutlimitation the rights to use, copy, modify, merge, publish,distribute, and/or sell copies
ofthe Software, and to permit personsto whom the Software is furnished to do so, provided that the abovecopyright
notice(s)and this permission notice appear in all copiesof the Software and that both the above copyright notice(s) and
thispermissionnotice appear in supporting documentation.
 
........

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.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: Collations and Replication; Next Steps
Next
From: Peter Geoghegan
Date:
Subject: Re: Collations and Replication; Next Steps