in reply to Re: Selling your Perl app
in thread Selling your Perl app

I'm just assuming that what ever you've built, it has CPAN modules in it. You're really going to have to do your homework if you want to sell a product that's reliant on CPAN modules (ie, you may have to negotiate a separate license from the module creator - if you can find him/her). *Or* you would have to package your application in such a way that part of it is *free* and part of it is not.

IANAL, but I think all CPAN modules that are distributed under the "same terms as perl itself" can be used without problem in closed source, commercial applications. Just the like the core modules that come with perl itself.

This might not apply to GPL-only modules. If you use a module, one might argue that it's the same as with linking against a GPL'ed library, in which case the whole application must be GPL'ed.

Replies are listed 'Best First'.
Re: OT: Licenses on CPAN (was: Re: Selling your Perl app)
by derby (Abbot) on May 08, 2008 at 13:09 UTC

    From the CPAN FAQ:

    How are Perl and the CPAN modules licensed?

    Most, though not all, modules on CPAN are licensed under the GNU Public License (GPL) or the Artistic license and should be stated in the documentation that accompanies the module itself. If the license is not specifically stated in the module, you can always write the author to clarify the issue for you. Also, the text of the Artistic license and the GNU Public License are included in the root directory of the source distribution. From the 'README' file that comes with Perl: ....

    So ... like I said, the OP needs to do his homework.

    -derby