Skip Menu |

This queue is for tickets about the Net-Sharktools CPAN distribution.

Report information
The Basics
Id: 65242
Status: resolved
Priority: 0/
Queue: Net-Sharktools
People
Owner: nanis [...] runu.moc.invalid
Requestors: jpo [...] di.uminho.pt
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in:
  • 0.003
  • 0.004
  • 0.005
Fixed in: 0.003

History Show all quoted text
  Sat Jan 29 12:33:55 2011 jpo [...] di.uminho.pt - Ticket created
Subject: Net-Sharktools: license Artistic_v2 or GPLv2
Hi, I have a question regarding the Net::Shartools license: shouldn't it be GPLv2 instead of Artistic_v2? Or is the Artistic_v2 license compatible with GPL? As stated in the sharktools v0.1.5 COPYING file, its libraries are licensed under the GPLv2 and not LGPL (see below). And at least in Linux Net::Sharktools is linked statically against sharktools (libsharktools.a). -------------------- ... Part I: Since Sharktools integrates parts of Wireshark into itself, Sharktools is being distributed under the GNU GPLv2. Sharktools is distributed under the GNU GPLv2. There are no restrictions on its use. There are restrictions on its distribution in source or binary form. Parts of Sharktools can be built and distributed as libraries. These parts are still covered by the GPL, and NOT by the Lesser General Public License or any other license. If you integrate all or part of Sharktools into your own application, then that application must be released under a license compatible with the GPL. ... -------------------- Regards, jpo PS - And thanks for sharktools' perl wrapper.
  Tue Feb 01 11:14:12 2011 jpo [...] di.uminho.pt - Correspondence added
From: jpo [...] di.uminho.pt
Hi, In Net::Sharktools v0.008 the file Sharktools.xs is still licensed under Artistic v2. /jpo
  Fri Feb 04 05:48:43 2011 nanis [...] runu.moc.invalid - Correspondence added
On Tue Feb 01 11:14:12 2011, jpo@di.uminho.pt wrote: Show quoted text
> In Net::Sharktools v0.008 the file Sharktools.xs > is still licensed under Artistic v2.
Hello jpo: Thank you for your report. First, Version 2 of the Artistic License is compatible with GPL (see <http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses>), so, presumably, releasing Net::Sharktools under Artistic v2 was OK. After your questions, brian and I decided that releasing the module under GPLv2, i.e. the same terms as Wireshark and Sharktools and pyshark was more appropriate to eliminate any confusion. As you can tell from the history of commits on github, it took me a few iterations to make all the edits, and it looks like I missed the most obvious one. I am going to fix that in a little bit and I am marking this report as "fixed" and closing it in anticipation. Thank you. -- Sinan
  Fri Feb 04 05:48:44 2011 The RT System itself - Status changed from 'new' to 'open'
  Fri Feb 04 05:48:44 2011 nanis [...] runu.moc.invalid - Status changed from 'open' to 'resolved'
  Fri Feb 04 05:48:44 2011 nanis [...] runu.moc.invalid - Given to NANIS
  Fri Feb 04 11:18:59 2011 jpo [...] di.uminho.pt - Correspondence added
From: jpo [...] di.uminho.pt
Sinan, Thank you for the license clarification - it will make life easier for packagers. And for speaking of packaging, I do have a draft specfile for perl-Net-Sharktools available here: * http://um-pe09-2.di.uminho.pt./fedora/perl-Net-Sharktools.spec It allows perl-Net-Sharktools to be build for Fedora (13, 14, 15) and RHEL 6 if you have the wireshark >= 1.4.3-2 RPMS available. Right now they are only available for Fedora 15 but its SRPM can be built in the distributions mentioned before (archs tested: i386 and x86_64). Regards, jpo References: * perl-Net-Sharktools SRPM in the same base directory: http://um-pe09-2.di.uminho.pt./fedora/perl-Net-Sharktools-0.009-0.el6.src.rpm * wireshark 1.4.3-2 SRPM: http://download.fedora.redhat.com/pub/fedora/linux/development/source/SRPMS/wireshark-1.4.3-2.fc15.src.rpm
  Fri Feb 04 11:19:00 2011 The RT System itself - Status changed from 'resolved' to 'open'
  Fri Feb 04 11:22:03 2011 jpo [...] di.uminho.pt - Correspondence added
From: jpo [...] di.uminho.pt
Oops! The ticket status changed to "open" and I can't close it ...
  Fri Feb 04 11:52:50 2011 nanis [...] runu.moc.invalid - Correspondence added
Thank you. I am sure that will allow many others to test the package. -- Sinan
  Fri Feb 04 11:52:51 2011 nanis [...] runu.moc.invalid - Status changed from 'open' to 'resolved'