Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

The Problem with the "Same Terms as Perl" Licensing 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It may not be so obvious to a lawyer but quite obviously "same terms as Perl" means the same terms as already accepted by using the version of Perl you're using the module with.

    If the you prefer the Perl[1234] license and the module works with Perl[1234], knock yourself out. But unless I'm using Perl 1, the Perl 1 license doesn't apply - I never used Perl[123] so I've never accepted their licenses. Haven't used Perl4 at current $DayJob so that doesn't touch *me* there, and we've I think stamped out all

    --
    Bill
    # I had a sig when sigs were cool
    use Sig;

    • It may not be so obvious to a lawyer but quite obviously "same terms as Perl" means the same terms as already accepted by using the version of Perl you're using the module with.

      Perhaps from the practical standpoint this is true -- why would I distribute software that you can't actually use? -- but there's at least one court case active right now where one side is arguing in all seriousness that distributing software under the Artistic License means that you're not interested in protecting your copyright. "Obvious" has very little place in the law, sadly.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.