wine license change - look at how ghostscript is licensed
marcus at jet.franken.de
Fri Feb 8 01:06:48 CST 2002
On Thu, Feb 07, 2002 at 05:44:36PM -0500, dschwarz at bellatlantic.net wrote:
> As a non-coder but longtime interested observer of the WINE project, here
> are my ideas:
> Consider doing what ghostscript does (http://www.ghostscript.com/). New
> versions are released under the AFPL license (more restrictive than GPL).
> Old versions are re-released under GPL when they are about 1 year out of
> This may be applicable to Wine. Like Wine, ghostscript tracks an evolving
> API. Older versions are useful but may not have all the latest bells and
> whistles. Those that need to be on the cutting edge have to use the more
> restrictive license.
If WINE should switch to the AFPL, I will:
- Delete all traces of WINE from my harddisk and the distributions I am
- Deny that I have ever done something for WINE or even heard of it.
The AFPL is by far the worst thing that could happen to WINE short of MS
ordering us to cease and desist.
More information about the wine-devel