Bug #19807 for Module-Install: Default license value to "restrictive"

Fri Jun 09 13:01:02 2006 Guest - Ticket created

Subject:

Default license value to "restrictive"

Although we often ignore licensing issues and hope they go away, the people downstream of us often do not. If a license is not specified, and cannot be detected via license_from or all_from, we should default the license value to "restrictive". This will ensure that anything that gets uploaded to CPAN can be confirmed to be legally allowable on the CPAN.

Sun Jan 28 00:50:35 2007 avar [...] cpan.org - Correspondence added

I concur with this request for similar reasons. When building propritery software with Module::Install the only choices of licenses are free software licenses and 'unknown'. Restrictive would both cover things that are by default seen as non-free and things that wish to stay that way. The attached patch implements this.

diff -ru Module-Install-0.64/inc/Module/Install/Metadata.pm Module-Install/inc/Module/Install/Metadata.pm --- Module-Install-0.64/inc/Module/Install/Metadata.pm 2006-08-23 17:12:48.000000000 +0000 +++ Module-Install/inc/Module/Install/Metadata.pm 2007-01-28 05:45:41.000000000 +0000 @@ -309,7 +309,7 @@ } warn "Cannot determine license info from $file\n"; - return 'unknown'; + return 'restrictive'; } 1;

Sun Jan 28 00:50:49 2007 The RT System itself - Status changed from 'new' to 'open'

Thu Jul 17 13:18:02 2008 adamk [...] cpan.org - Correspondence added

There is a 'proprietary' license option for explicitly non-open work, and 'unknown' is already considered non-open. And unknown is also less presumptuous. Leaving it as is.

Thu Jul 17 13:18:04 2008 adamk [...] cpan.org - Status changed from 'open' to 'rejected'