Bug#530615: ITP: libfile-temp-perl -- return name and handle of a temporary file safely
On Tue, 2009-26-05 at 11:05 -0400, Jonathan Yu wrote: > However, I think within the Perl community, this is something that is > already widely understood -- that is, dual-lived modules. This is a 'debian' list ... -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#487125: rdepend
On Fri, 2010-30-04 at 19:16 +0200, Bastien ROUCARIES wrote: > Hi guy, > > Do you intend to be mainteners of rdepends ? I forgot all about that. I think when I looked there was nothing much to do ... you can have it if you like. > > I could help you if needed > > bastien -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1272647886.8840.757.ca...@cray.home.cotef.net
Bug#580533: ITP: libtest-notabs-perl -- module for scanning for hard tabs in files
On Thu, 2010-06-05 at 12:26 -0400, Jonathan Yu wrote: > 0x09) character. Tabs can render with slightly different width depending on > the author's environment, so it's best to use spaces instead. how obnoxious -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1273163556.8840.1356.ca...@cray.home.cotef.net
Bug#487125: apt-rdepends
On Sun, 2010-06-06 at 17:54 +0200, Axel Beckert wrote: > If you're still interested in helping out: I wouldn't mind a > co-maintainer. Do as you see fit. You may remove me from the email list for the bug or not as you please. I am very busy at the moment. I might have a go at doing some debian work in 6 months or so. -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1275845143.19710.79.ca...@cray.home.cotef.net
Bug#534338: OpenSSL bindings for Perl -- licensing questions
On Wed, 2012-27-06 at 07:27 -0400, Daniel Kahn Gillmor wrote: [snip] > I don't believe #534338 covered Crypt::OpenSSL::AES. However, i do > wonder whether Crypt::OpenSSL::AES has received permission from the > OpenSSL upstrem for the use of the term "OpenSSL" in its name, as > referred to at: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534338#20 > [snip] It depends what "derived from this software" means. The only protection "OpenSSL" has, in itself, would be as a trademark. Apple has an example here: http://www.apple.com/legal/trademark/appletmlist.html which seems to indicate that "OpenSSL Project" and "OpenSSL Toolkit" are protected but not bare "OpenSSL". It also indicates that the restrictions imposed are only using the "openssl" name for marketing. But Apple has a written agreement with OpenSSL. -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1340802015.26197.48.ca...@cray.home.cotef.net
Bug#534338: OpenSSL bindings for Perl -- licensing questions
On Wed, 2012-27-06 at 10:03 -0400, Daniel Kahn Gillmor wrote: > Given that the perl modules in question clearly contain "OpenSSL" in > their names, this appears to only be satisfied under one of the > following conditions: > > 0) a perl module is not a "product" > 1) these perl modules are not "derived from" OpenSSL I think this is the best argument. > 2) the OpenSSL Project has given these modules explicit permission > 3) this clause is considered unenforceable and/or somehow > illegitimate It's unenforcable if the modules in question do not incorporate any OpenSSL code and are just an interface to the library. I think this is probably the case. There seem to be between 30 and 40 modules on CPAN with OpenSSL in the name and no-one seems to be bothered. -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1340815129.26197.57.ca...@cray.home.cotef.net
Bug#534338: OpenSSL bindings for Perl -- licensing questions
On Wed, 2012-27-06 at 12:49 -0400, Daniel Kahn Gillmor wrote: > On 06/27/2012 12:38 PM, Guy Hulbert wrote: > > It's unenforcable if the modules in question do not incorporate any > > OpenSSL code and are just an interface to the library. I think this is > > probably the case. > > Eh? How is a binding to a library not a project that is "derived from" > that library? I don't follow your explanation that the clause is > unenforcable. What makes it unenforcable? Because if I write the code, I own it. So in the case of a perl module I can call it anything I want unless there is a trademark involved (and, i believe trademarking words is a perversion). Please just disregard my input if you want to play lawyer. I will stop now. -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1340815948.26197.66.ca...@cray.home.cotef.net
Bug#534338: OpenSSL bindings for Perl -- licensing questions
On Wed, 2012-27-06 at 13:42 -0400, Mike O'Connor wrote: > On Wed, Jun 27, 2012 at 12:52:28PM -0400, Guy Hulbert wrote: > > On Wed, 2012-27-06 at 12:49 -0400, Daniel Kahn Gillmor wrote: > > > On 06/27/2012 12:38 PM, Guy Hulbert wrote: > > > > It's unenforcable if the modules in question do not incorporate any > > > > OpenSSL code and are just an interface to the library. I think this is > > > > probably the case. > > > > > > Eh? How is a binding to a library not a project that is "derived from" > > > that library? I don't follow your explanation that the clause is > > > unenforcable. What makes it unenforcable? The stuff on CPAN is source. So it's not linked to anything. It may have instructions to link to something but OpenSSL has no legal authority to stop that. > > > > Because if I write the code, I own it. So in the case of a perl module > > I can call it anything I want unless there is a trademark involved (and, > > i believe trademarking words is a perversion). > > > > In this case *some* of the code was written by the authors of the perl > code, but much of the source code comes directly from openssl. The perl > module author is taking a lot of code from openssl, adding some of their > own, them compiling that together into a new work. This is clearly a > derrivative work. Define "derivative". Until it's compiled, it's not. > > Look, for example at the source code to libcrypt-openssl-rsa-perl. In > RSA.xs, these lines appear: > > #include > #include > #include > #include > #include > #include > #include > #include > #include > #include > #include > > Those are instructions to the compiler to directly include source code > from the openssl project. Tha *compiler*. So it might be a problem for Debian except that Debian is NOT using the string "OpenSSL". It is using the lower-case version. So there's no violation ... though IANAL. IMO, if Debian is to do anything, it should first contact the "OpenSSL Project" to see if there's a problem. Harassing CPAN authors seems premature to me. > > stew -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1340819651.26197.73.ca...@cray.home.cotef.net
Bug#534338: OpenSSL bindings for Perl -- licensing questions
On Wed, 2012-27-06 at 14:25 -0400, Daniel Kahn Gillmor wrote: > On 06/27/2012 01:54 PM, Guy Hulbert wrote: > > Define "derivative". Until it's compiled, it's not. > > Right. Unfortunately for debian, and any other binary distributor of > CPAN modules, we distribute it compiled. > > > Tha *compiler*. So it might be a problem for Debian except that Debian > > is NOT using the string "OpenSSL". It is using the lower-case version. > > So there's no violation ... though IANAL. > > Wow, there's a way to thread the needle that hadn't occurred to me. Was > this what you were trying to point out before? I have my doubts about I had not thought carefully initially the whole discussion is so ridiculous on its face that I just reacted. I told you once you could ignore me. > the legitimacy of the case of the package name as a differentiator, > frankly, but i suppose that's one approach to take. Should we also > change the case of the man pages and the paths to the .pm files? This is clearly ridiculous. I was just referring to the debian package name. I thought that was obvious from context. > > > IMO, if Debian is to do anything, it should first contact the "OpenSSL > > Project" to see if there's a problem. Harassing CPAN authors seems > > premature to me. > > I'm not sure how the debian project can ask the OpenSSL project for > written permission to use the string in these projects, since: Perhaps you should first get written permission to use the OpenSSL string in this email thread. [snip] -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1340821943.26197.79.ca...@cray.home.cotef.net
Bug#534338: OpenSSL bindings for Perl -- licensing questions
On Wed, 2012-27-06 at 23:13 +0200, Kai Storbeck wrote: > I'm a bit perplexed that the module authors have anything to do with > this as long as they are clearly stating their code is released under > the artistic license. This is my position, stated somewhat more clearly. The particular license of the module does not matter as long as it follows DFSG. > Should Debian concern itself (too much) with the authority of such a > claim? Is it debians task to mediate between all open source forges > around the world and their claims for licensing? In this case, Debian could ask for a clarification from or a suitable agreement (as Apple has done) with OpenSSL. The problem for Debian is that Debian is not just distributing the source code from CPAN and OpenSSL has a weird clause (#5) in their license. > > Apologies if this is in the debian policy. -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1340834109.26197.98.ca...@cray.home.cotef.net
Bug#487125: RFA: apt-rdepends -- Recursively lists package dependencies
On Fri, 2009-10-04 at 13:01 +0200, Cristian Greco wrote: > I'm looking for a new maintainer for the package apt-rdepends, and CCing to > the > debian-perl list as I hope someone with good Perl programming skills could be > interested in upstream-maintenance of this script. I could do this. This package would be a dependency for something I am doing. Presently, I'm using the output of `apt-get -s install ...` > > Well, for the sake of sincerity, I declared my ITA about one year ago, but I > was really unable to pay so much attention to this package, mostly due to my > lack of Perl skills (as this script is much more and hack than a well-written > piece of software). > > I'd be glad if someone from the pkg-perl team could be interested in > maintaining this package, but if I don't receive replies in a reasonable > timeframe, I'll formally (re)orphan it. I'm not a member of the team but I'm lurking on the list for some time now. -- --gh -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
