rev-upgrade to determine if binary is distributable

[Jeremy Lavergne]

> Hop down to "array set license_conflicts"  in the code.
> 
> These are the conflicts Apache license has with other licenses:
>    apache {cecill gpl-1 gpl-2}
>    apache-1 {agpl gpl}
>    apache-1.1 {agpl gpl}

This has me wondering: is the code interpreting "apache" to be all versions of apache? If the version is missing, I thought it was suppose to default to 0.

From the Guide:
The proper format for license consists of the license name, followed by a hyphen and number if indicating a specific version. 
...
If the version number is a “.0” version, the “.0” should be omitted to make the version an integer.

Ah, so all Apache licenses conflict with gpl-1 and gpl-2.

> Notice gpl-3 is not conflicted, ergo gpl-2+ is not conflicted.
> 
> Same with GPL conflicts:
>    gpl {afl agpl apache-1 apache-1.1 apsl beopen cnri bsd-old cpl epl gd gplconflict ibmpl lppl mpl noncommercial openssl php qpl restrictive/distributable ruby ssleay zpl-1}
>    gpl-1 {apache gpl-3 gpl-3+ lgpl-3 lgpl-3+}
>    gpl-2 {apache freetype gpl-3 gpl-3+ lgpl-3 lgpl-3+}
>    gpl-3 {gpl-1 gpl-2}
>    gpl-3+ {gpl-1 gpl-2}
> 
> None of them conflict with apache-2, only 1.0 and 1.1. See all the Apache license versions here:
> http://www.apache.org/licenses/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 8796 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20120607/2770e455/attachment-0001.bin>