Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-03-24 Thread fabian
Hi Jonas, Am 18.02.2011 11:33, schrieb Jonas Smedegaard: 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

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-03-24 Thread Bastien ROUCARIES
agree On Thu, Mar 24, 2011 at 12:48 PM, fab...@greffrath.com wrote: Hi Jonas, Am 18.02.2011 11:33, schrieb Jonas Smedegaard: 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:

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-03-24 Thread Jonas Smedegaard
On Thu, Mar 24, 2011 at 12:48:49PM +0100, fab...@greffrath.com wrote: Am 18.02.2011 11:33, schrieb Jonas Smedegaard: 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:

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-03-24 Thread fabian
Thing is, gsfonts is not mine to deal with. But that shouldn't stop others (yourself, Fabian?) from packaging URW++ fonts from its true source - and then change this bugreport into a request for removal of that (then obsolete) package. With separate package I meant another binary package

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-03-24 Thread Jonas Smedegaard
On Thu, Mar 24, 2011 at 02:23:23PM +0100, fab...@greffrath.com wrote: Thing is, gsfonts is not mine to deal with. But that shouldn't stop others (yourself, Fabian?) from packaging URW++ fonts from its true source - and then change this bugreport into a request for removal of that (then

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-02-19 Thread Fabian Greffrath
Am Freitag, den 18.02.2011, 12:51 +0100 schrieb Jonas Smedegaard: That's what I am talking about: The Ghostscript project includes all needed resources as part of a single tarball instead of as isolated chunks. Indeed, I understood your initial response the other way round. ;) Debian has a

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-02-18 Thread Fabian Greffrath
Package: libgs9-common Version: 9.01~dfsg-1 Severity: normal Hi Jonas, is there a reason why ghostscript ships its own fonts in /usr/share/ghostscript/9.01/Resource/Font in the libgs9-common package but also depends on the gsfonts package? The latter contains modified variants of the exact same

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-02-18 Thread Jonas Smedegaard
On Fri, Feb 18, 2011 at 10:07:32AM +0100, Fabian Greffrath wrote: is there a reason why ghostscript ships its own fonts in /usr/share/ghostscript/9.01/Resource/Font in the libgs9-common package but also depends on the gsfonts package? The latter contains modified variants of the exact same

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-02-18 Thread Fabian Greffrath
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

Bug#613912: ghostscript ships its own fonts in libgs9-common, additionally depends on gsfonts

2011-02-18 Thread Jonas Smedegaard
On Fri, Feb 18, 2011 at 11:43:57AM +0100, Fabian Greffrath wrote: 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