Re: Bug#458385: New version of Artistic License
While on principle I agree with Charles Plessy about the merits of
including this license despite not having the "critical mass" that
Debian would like, I understand the view of those in the policy team
and respect their decision.
For what it's worth, I've added a
machine-readable-copyright-format-compatible Artistic-2.0 license text
to: http://pkg-perl.alioth.debian.org/copyright.html -- in reality,
I've only come across a few Artistic-2.0 licensed modules (the rest
are semi-ambiguous "same terms as Perl" -- which gets confusing with
the abundance of Perl6:: modules, but I digress).
I still consider having to copy-and-paste that license (and later
having to remove it and replace it with a reference to the one in
common-licenses) papercuts -- they're annoying, but not the end of the
world. And I guess we won't have to worry about removing them for
another few years yet.. so we can let future-me deal with it :-)
On Sun, Aug 30, 2009 at 2:35 AM, Charles Plessy<firstname.lastname@example.org> wrote:
> Le Sat, Aug 29, 2009 at 02:23:26PM +0200, gregor herrmann a écrit :
>> As a first approach I've grepped thruugh the lintian lab:
>> gregoa@bellini:/org/lintian.debian.org/laboratory/source$ egrep "(Artistic License (Version )*2|Artistic-2)" */debfiles/copyright | cut -f1 -d/ | uniq | wc -l
> Interestingly, this list does not fully overlap with the result of a search for
> "The Artistic Licence 2.0" using OpenGrok.
> This said, I would like to add my voice to say that since there are good
> reasons to think that the Artistic license 2.0 will become a common license
> some days, even if it takes a few years, it would be kind to add it in the
> common license list in advance, to save the maintainer's time from adding it to
> debian/copyright now and removing later.
> Have a nice day,
> Charles Plessy
> Debian Med packaging team,
> Tsurumi, Kanagawa, Japan
> To UNSUBSCRIBE, email to debian-policy-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com