Skip Menu |

This queue is for tickets about the Tree-DAG_Node CPAN distribution.

Report information
The Basics
Id: 83088
Status: resolved
Priority: 0/
Queue: Tree-DAG_Node

People
Owner: Nobody in particular
Requestors: paul [...] city-fan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 1.10
Fixed in: (no value)



Subject: License ambiguity
In the new release 1.10, the CPAN metadata suggests a license change from "perl" to "artistic_2" but there's no mention of this in the CHANGES file, and the POD still says the code is licensed the same as Perl itself. Was the metadata change inadvertent?
Subject: Re: [rt.cpan.org #83088] License ambiguity
Date: Sat, 02 Feb 2013 07:18:09 +1100
To: bug-Tree-DAG_Node [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Paul On 01/02/13 20:01, paul@city-fan.org via RT wrote: Show quoted text
> Fri Feb 01 04:01:48 2013: Request 83088 was acted upon. > Transaction: Ticket created by paul@city-fan.org > Queue: Tree-DAG_Node > Subject: License ambiguity > Broken in: 1.10 > Severity: (no value) > Owner: Nobody > Requestors: paul@city-fan.org > Status: new > Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=83088> > > > In the new release 1.10, the CPAN metadata suggests a license change > from "perl" to "artistic_2" but there's no mention of this in the > CHANGES file, and the POD still says the code is licensed the same as > Perl itself. Was the metadata change inadvertent?
Build.PL has the change as intended, but it's my fault that CHANGES and *.pm were not changed to match. I'll release another version ASAP. Other (as-yet unreleased) modules have the same problem. It looks like I rolled-back my repositories and did not realize I'd zapped the output of a script which updated all CHANGES and Build.PL files. -- Ron Savage http://savage.net.au/ Ph: 0421 920 622
Hi Fixed in V 1.11.