Am 18.02.2011 11:33, schrieb Jonas Smedegaard:
There are multiple reasons, e.g. historical packaging complications, historical packaging cleanup complications, and the fact that upstream treat external codebases as local sources, the latter causing additional burden of our side of analysing and ripping apart the various parts again.
Not anymore. IIRC starting with Ghostscript 8.60 (i.e. the one that combined the AFPL, GPL and ESP versions) the ghostscript release tarball also included the fonts in Ressource/Font (the ones that were only available as a separate download before). So strictly speaking, this was the moment when one of both font sets became obsolete.
I agree, however, with the message between the lines of your question: There is no _sensible_ reason :-)
There is currently a discussion on gs-devel to merge the urwcyr 1.0.7pre44 fonts that Debian ships in their gsfonts package into the fonts that ghostscript ships: <http://ghostscript.com/pipermail/gs-devel/2011-February/008891.html>
So maybe this problem is solved upstream and Debian can finally stop shipping two slightly different font sets in its ghostscript and gsfonts packages.
So thanks for pointing this out! It is indeed a bug.
;) - Fabian