in reply to GPL and Perl Artistic License for CPAN Modules

I don't know of an easy way to do this, but if you still have the untarred module sources available you could do a search through those (with egrep -ri '(artistic|gpl)' or a more suitable variation thereof), or check the modules perldoc, most of those contain the appropriate licensing notice at the bottom. Otherwise, if you've got the modules installed on your system, check the place were your system usually puts documentation/licensing information (on Debian Linux that would be /usr/share/doc/<package-name>). Or browse the modules files on CPAN.

As a last resort (and really as a last resort, you shouldn't bother people unless you're sure this information is missing) you can email the module author and ask him to clarify the license for you.


Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

Replies are listed 'Best First'.
Re^2: GPL and Perl Artistic License for CPAN Modules
by grinder (Bishop) on Dec 09, 2005 at 11:25 UTC
    with egrep -ri '(artistic|gpl)' or a more suitable variation thereof

    I think that:

    egrep -ri '(artistic|gpl|same terms as perl itself)'

    ...would be a very good variation :) I know my modules don't specifically mention Artistic or GPL textually. Nor do many others that I use regularly (but with the above term, they are explicitly available under Artistic or GPL).

    • another intruder with the mooring in the heart of the Perl

[reply]
[d/l]

In Section Seekers of Perl Wisdom