Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-07 Thread Christophe-Marie Duquesne
FYI, I asked the question on debian-legal (no answer yet). http://lists.debian.org/debian-legal/2012/07/msg00012.html -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.o

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Bart Martens
On Fri, Jul 06, 2012 at 11:35:34AM +0200, Christophe-Marie Duquesne wrote: > I take the > header of the closed-source library, wipe out the comments and (...) In that case I see no doubt that you start from the closed-source work. I have read other comments in this thread suggesting different app

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Russ Allbery
Roger Leigh writes: > To avoid any implication that anything from the headers has been copied, > why not just use the output of "nm [-D]". This is the interface that > programs use to link with the library, and is what you need to provide > as a drop-in replacement. I'm also not a lawyer, and y

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Will Dowling
> PS: the project in question is more a "proxy" towards the closed > source library than a real reimplementation, but technically I > actually reimplement every function of their header. If you are > interested, it is hosted here [2]. In addition to the debian-legal list, you might want to speak

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Gergely Nagy
Christophe-Marie Duquesne writes: > On Fri, Jul 6, 2012 at 2:40 PM, Roger Leigh wrote: >> To avoid any implication that anything from the headers has been >> copied, why not just use the output of "nm [-D]". This is the >> interface that programs use to link with the library, and is >> what you

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Christophe-Marie Duquesne
On Fri, Jul 6, 2012 at 2:40 PM, Roger Leigh wrote: > To avoid any implication that anything from the headers has been > copied, why not just use the output of "nm [-D]". This is the > interface that programs use to link with the library, and is > what you need to provide as a drop-in replacement.

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Roger Leigh
On Fri, Jul 06, 2012 at 11:35:34AM +0200, Christophe-Marie Duquesne wrote: > I want the libary to be a fully compatible runtime and compile-time > replacement for the closed-source one, so I have no choice but to use > the exact same symbol names in my header. What I do is I take the > header of th

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Christophe-Marie Duquesne
On Fri, Jul 6, 2012 at 1:22 PM, Gergely Nagy wrote: > If it is a proxy, then it is not a reimplementation. That you add a > wrapper for every function, doesn't matter, you still call the original. Yes, it is meant to be a proxy. > If it would be a reimplementation, the best course of action woul

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Michael Wild
On 07/06/2012 01:22 PM, Gergely Nagy wrote: > Christophe-Marie Duquesne writes: > >> I am the author of an opensource library that reimplements a >> closed-source library. > [...] >> PS: the project in question is more a "proxy" towards the closed >> source library than a real reimplementation, b

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Gergely Nagy
Christophe-Marie Duquesne writes: > I am the author of an opensource library that reimplements a > closed-source library. [...] > PS: the project in question is more a "proxy" towards the closed > source library than a real reimplementation, but technically I > actually reimplement every function

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Christophe-Marie Duquesne
On Fri, Jul 6, 2012 at 1:19 PM, Nicolas Bourdaud wrote: > I think the best would be to ask on the dedicated mailing list: > debian-le...@lists.debian.org Hi, I did not know about debian-legal. I'll ask there. Thank you! -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org wit

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Nicolas Bourdaud
Hi, On 06/07/2012 11:58, Christophe-Marie Duquesne wrote: > On Fri, Jul 6, 2012 at 11:41 AM, Andrey Rahmatullin wrote: >> We are not lawyers, but see the recent Google v. Oracle lawsuit. >> Of course that's only USA law and USA court, but you cannot get one answer >> for the whole world. > > >

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Christophe-Marie Duquesne
On Fri, Jul 6, 2012 at 11:41 AM, Andrey Rahmatullin wrote: > We are not lawyers, but see the recent Google v. Oracle lawsuit. > Of course that's only USA law and USA court, but you cannot get one answer > for the whole world. I completely understand that there are no lawyers on this mailing list

Re: Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Andrey Rahmatullin
On Fri, Jul 06, 2012 at 11:35:34AM +0200, Christophe-Marie Duquesne wrote: > I want the libary to be a fully compatible runtime and compile-time > replacement for the closed-source one, so I have no choice but to use > the exact same symbol names in my header. What I do is I take the > header of th

Copyright problems for the opensource reimplementation of a closed-source library (ITP #679504)

2012-07-06 Thread Christophe-Marie Duquesne
Hi, I am the author of an opensource library that reimplements a closed-source library. I want the libary to be a fully compatible runtime and compile-time replacement for the closed-source one, so I have no choice but to use the exact same symbol names in my header. What I do is I take the heade