Re: Name restriction and forced acknowledgement OK?

2012-02-21 Thread Osamu Aoki
Hi, On Mon, Feb 13, 2012 at 05:05:37PM +, MJ Ray wrote: ... > Whatever good intentions they may have, they should not deny users the > freedoms to implement functions in different ways (iauEpj2jd_cached), > or to combine it with another library that includes a function called > iauque (for exa

Re: Name restriction and forced acknowledgement OK?

2012-02-13 Thread Mark Weyer
On Mon, Feb 13, 2012 at 12:23:45PM +0100, Olе Streicher wrote: > Mark Weyer writes: > > On Mon, Feb 13, 2012 at 10:19:04AM +0100, Ole Streicher wrote: > >> c. The name(s) of all routine(s) in your derived work shall not > >> include the prefix "iau". As you mentioned macros versus fu

Re: Name restriction and forced acknowledgement OK?

2012-02-13 Thread Olе Streicher
MJ Ray writes: >> Why? It just requires that they get a different name. > I would have said it fails DFSG 4. One rename is fine, but this > requires that everything is renamed, which is a practical pain in the > bum for no good effect, and tries to grab an infinite number of names. It requires

Re: Name restriction and forced acknowledgement OK?

2012-02-13 Thread MJ Ray
debian-de...@liska.ath.cx (Olе Streicher) > Mark Weyer writes: > > On Mon, Feb 13, 2012 at 10:19:04AM +0100, Ole Streicher wrote: > >> c. The name(s) of all routine(s) in your derived work shall not > >> include the prefix "iau". > > Non-free: It effectively forbids using a modified l

Re: Name restriction and forced acknowledgement OK?

2012-02-13 Thread Olе Streicher
Mark Weyer writes: > On Mon, Feb 13, 2012 at 10:19:04AM +0100, Ole Streicher wrote: >> -8<- > In general, people on this list tend to prefer full license texts plus the > boilerplate. I'll put the full text at the end. >> c

Re: Name restriction and forced acknowledgement OK?

2012-02-13 Thread Mark Weyer
On Mon, Feb 13, 2012 at 10:19:04AM +0100, Ole Streicher wrote: > -8<- > [...] In general, people on this list tend to prefer full license texts plus the boilerplate. > 3. You [...] may [...] adapt its code [...] That portio

Name restriction and forced acknowledgement OK?

2012-02-13 Thread Ole Streicher
Dear list members, I intent to package the ANSI C library of IAU-SOFA , which has a non-usual (?) license agreement . Especially, I worry about two points: 1. Not allowed to use the original names in changed code: