Ghostscript went GPL! News items in English: http://lxer.com/module/newswire/view/63031/index.html News items in German: http://www.golem.de/0606/45942.html http://www.heise.de/newsticker/meldung/74347 It remains to be seen what implications this will have w/ regards to the other forks (merges would be great), but I guess it should be in Portage (quite a jump from 8.16 to 8.54). The latest release v8.54 under GPL (gpl-ghostscript) is already on SF.
Well, so... what to go w/ this ebuild? Merge ghostscript-afpl w/ gnostscript-gnu? Better ideas? Otherwise, this will get really confusing.
ok, the plan is: - mark ghostscript-afpl-8.54-r1 stable, so that I only have to migrate the latest version. - move ghostscript-afpl-8.54-r1 to ghostscript-gpl-8.54-r1 and change the tarball source as well as the license - make ghsotscript-gpl the default for virtual/ghostscript we then have: ghostscript-esp - with special patches for cups support, but old. ghostscript-gnu - made by the GNU people with special GPL patches that cannot be made afpl. Lacking behind a lot lately ghostscript-gpl - the latest -afpl release rereleased under the GPL, this is what would be preferred.
(In reply to comment #1) > Well, so... what to go w/ this ebuild? Merge ghostscript-afpl w/ > gnostscript-gnu? Better ideas? Otherwise, this will get really confusing. Ah, I forgot to suggest an "action plan" and wrote more like a notification... Anyway, what Stefan suggests (comment #3) is a good idea; ghostscript-afpl should definitely be phased out. Thanks for your quick reply.
Stable on amd64, this is the most stable version I have used on my amd64 boxes and it is great to see their move to GPL the source. Stable on amd64 :)
ppc stable
x86 done ^.^
This is now really fixed :) I moved it to -gpl and changed the license and the default in the virtual, thanks!
