I found Ben's dual licensing not clear at all (and explanations and
comments even less).
•GPL v3 license when shipped as part of a programming language, its core
libraries and frameworks, or its Integrated Development Environment.
•MIT license for other cases.
As I finally understand it, Pharo would be GPL v3 in all cases.
A killer change
But as stated in the license agreement (the one found on the old pharo
site):
"... Supplier hereby grants Distributor a perpetual, irrevocable,
non-exclusive, royalty-free, worldwide license to distribute the
Software, and specifically the Supplier’s Code therein, to end users,
subject to the license agreement commonly known as the “MIT License” "
Ben can change the license of the code he writes to GPL and stop this
agreement at that point, but the change in the license is not
retroactive, the Pharo version will have to start before revision xxx
where it changed and go on it's way.
Still there will be a problem in the repository(ies).
