|Subject:||CPAN::Meta::Converter should probably map gpl to open_source|
For an example of the problem, seeBasically, when "gpl" is specified in Build.PL, it ends up as "gpl_1" in META.json. Here I quote a conversation from #toolchain, 2011-03-30 (all times in EDT, sorry): (03:31:34 PM) The topic for #toolchain is: the tools who yank our chains (03:31:49 PM) dapatrick: Hello rjbs. (03:31:51 PM) dapatrick: Hello xdg. (03:32:03 PM) dapatrick: mst told me to bug you guys. (03:32:16 PM) mst: rjbs: (03:32:30 PM) rjbs: STOP BUGGING ME (03:32:36 PM) rjbs: Alternately, what's up? (03:32:37 PM) mst: seems that Module::BUild plus CPAN::Meta::Converter are making a META.kson with license 'gpl_1' for license => 'gpl' (03:32:46 PM) mst: whereas in M::B previously 'gpl' generally meant "some version of the GPL" (03:33:04 PM) rjbs: Hm. (03:33:11 PM) dapatrick: ^ right, that (03:33:13 PM) dapatrick: (03:33:14 PM) dipsy: [ Roland Hu? / jmx4perl-0.90_3 - search.cpan.org ] (03:33:17 PM) rjbs: I am not sure that "some version" is legal in v2, let me check. (03:33:45 PM) rjbs: Yeah, so the problem is that the converter, rather than fall back to open_source, uses gpl_1. (03:33:49 PM) rjbs: One more sec. (03:34:35 PM) rjbs: Hm. Not seeing any upgrade_license code. (03:35:08 PM) rjbs: gpl => 'gpl_1', (03:35:30 PM) rjbs: Okay, so %license_map_2 in CPAN::Meta::Converter should probably map gpl to open_source; other licenses may be affected. (03:35:48 PM) rjbs: dapatrick: Can you file an RT request to that effect, and I'll have a look into it and talk to xdg? (03:36:01 PM) dapatrick: Sure. (03:36:02 PM) rjbs: I'm mid-workday atm, but I agree that this is almost certainly undesired behavior (03:36:06 PM) rjbs: Thanks.