On 8/29/15 8:52 AM, [email protected] wrote: > Revision > 139833 <https://trac.macports.org/changeset/139833> > Author > [email protected] > Date > 2015-08-29 08:52:17 -0700 (Sat, 29 Aug 2015) > > > Log Message > > p5-mozilla-ca: indicate multiple licensing as per MPL-2 > > > Modified Paths > > * trunk/dports/perl/p5-mozilla-ca/Portfile > <#trunkdportsperlp5mozillacaPortfile> > > > Diff > > > Modified: trunk/dports/perl/p5-mozilla-ca/Portfile (139832 => 139833) > > --- trunk/dports/perl/p5-mozilla-ca/Portfile 2015-08-29 15:35:50 UTC (rev > 139832) +++ > trunk/dports/perl/p5-mozilla-ca/Portfile 2015-08-29 15:52:17 UTC (rev 139833) > @@ -7,7 +7,7 @@ perl5.branches 5.16 5.18 > 5.20 5.22 perl5.setup Mozilla-CA 20150826 platforms darwin -license MPL-2 > +license {MPL-2 LGPL-2.1} maintainers > nomaintainer supported_archs noarch > > > > _______________________________________________ > macports-changes mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-changes >
Thanks, Josh. While you're thinking about licensing, what's the procedure for adding new licenses to those known by MacPorts and what they conflict with? In the upcoming 3.18 GNOME release many ports are switching to CC-BY-SA and various variants for documentation and icons. These are unknown to MacPorts currently but should not constitute any conflicts AFAICT (which doesn't mean much). Do we have a licensing guru? Is there a standard we go by? Dave _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
