Perl Tk license

Dale netxe456 at
Tue May 24 05:39:04 UTC 2011

>From a research I've done all applications written in Perl just import the
modules (like 'use Tk') into their source code, they don't ship with the
full source code of the module.I think that falls under your first category:
>>1. Distribute your application separately from the Perl Tk module and
>>require users to install the Perl Tk module (typical);

Should my source code distribution include a verbatim copy of each license
used ?
i.e if a module that I import is under Artistic License 1.0 and another one
under Artistic License 2.0, should I also include a copy of the license (in
a text file) or is just a URL link to the license sufficient?

and what about my binary distribution when I create one executable with all
those modules/components tied together with my source?
Is just a README file that says "the executable application uses Perl Tk
module,etc For Perl tk's license check the following URL...."
something along those lines.Is that sufficient?

thanks very much again

On Wed, Apr 20, 2011 at 10:13 PM, Derrick Coetzee <dc at> wrote:

> On Wed, Apr 20, 2011 at 4:55 AM, Dale <netxe456 at> wrote:
> > I want to write an application that uses the Perl Tk module and license
> my
> > code under GPL
> > It is the license of Perl Tk that buffles me :
> > [...]
> > What does that actually mean? where should I put those terms?
> > inside my application's source code distribution should I also include Tk
> > module's source code ?
> If you are only writing an application using the Perl Tk module, you
> have three choices:
> 1. Distribute your application separately from the Perl Tk module and
> require users to install the Perl Tk module (typical);
> 2. Distribute your application together with unmodified source of Perl
> Tk module;
> 3. Distribute your application with binaries of Perl Tk module, and
> put a copy of the Perl Tk license statement in your licenses file.
> If you're modifying the source of the Perl Tk module, you should
> include the source with the original license statement(s) and you can
> also add a license statement for your modifications in the files you
> modified. This is all pretty typical for use of an open source
> library/module in an application.
> --
> Derrick Coetzee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the License-discuss mailing list