After some reading the AGPLv3 license is not different from GPLv3 with one addition. Since many services now run in the cloud in AGPLv3 this is also covered as "distribution" of the code and must be done under the same rights that GPLv3 would require when shipping software as binary builds via some storage media.
We do not change anything to the "db v6" code base. A quick overview over the rebuilt packages I can't see a pkg that is published under a non-free license. If we would be allowed to link to DBv6 if it would be under GPLv3 then we are also allowed to link to it under AGPLv3. I see no serious reason to not accept that license change. http://en.wikipedia.org/wiki/Affero_General_Public_License#Compatibility_with_the_GPL http://lwn.net/Articles/557820/ http://en.wikipedia.org/wiki/GPL_linking_exception I'm no expert in that stuff. Maybe someone dealing day by day with such stuff has more knowledge here. -Andy
signature.asc
Description: PGP signature
