Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-26 Thread Till Kamppeter
On 01/25/2011 08:27 PM, Jonas Smedegaard wrote: Another argument for keeping libijs separate: I consider packaging GNU Ghostscript, which seem to have a slightly different development pace and thus might be interesting e.g. for security concerned users, and would also make the recent RC issue

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-26 Thread Till Kamppeter
On 01/25/2011 09:48 PM, Roger Leigh wrote: Just for the record, I think there should be *one* copy of ijs only. I really don't care whether it's in ijs or gs. However, given that gs is required for ijs to work, and the copy in gs has had some maintenance, I think the gs copy would be the better

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-26 Thread Till Kamppeter
On 01/25/2011 10:04 PM, Jonas Smedegaard wrote: I think perhaps you miss my point: If libijs is maintained for Debian as part of the GPL Ghostscript project, and we also (in the future) maintain GNU Ghostscript, then GNU Ghostscript will need to depend on GPL Ghostscript, making it impossible

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-26 Thread Jonas Smedegaard
On Wed, Jan 26, 2011 at 07:58:12PM +0100, Till Kamppeter wrote: On 01/25/2011 10:04 PM, Jonas Smedegaard wrote: I think perhaps you miss my point: If libijs is maintained for Debian as part of the GPL Ghostscript project, and we also (in the future) maintain GNU Ghostscript, then GNU

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-25 Thread Roger Leigh
On Mon, Jan 24, 2011 at 08:47:07PM +0100, Jonas Smedegaard wrote: Hi Till (and others), I took the liberty of moving this conversation to the Debian Printing Team and cc ijs package maintainer. On Mon, Jan 24, 2011 at 08:12:31PM +0100, Till Kamppeter wrote: as written on

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-25 Thread Roger Leigh
On Tue, Jan 25, 2011 at 08:27:38PM +0100, Jonas Smedegaard wrote: On Tue, Jan 25, 2011 at 06:59:08PM +, Roger Leigh wrote: I was the original packager and maintainer of ijs, and I was also involved with upstream when it was created, so I might be able to provide some insight here. I

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-24 Thread Jonas Smedegaard
Hi Till (and others), I took the liberty of moving this conversation to the Debian Printing Team and cc ijs package maintainer. On Mon, Jan 24, 2011 at 08:12:31PM +0100, Till Kamppeter wrote: as written on http://www.openprinting.org/download/ijs/ the current head of development of the IJS

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-24 Thread Till Kamppeter
On 01/24/2011 08:47 PM, Jonas Smedegaard wrote: Hi Till (and others), I took the liberty of moving this conversation to the Debian Printing Team and cc ijs package maintainer. OK, good idea. I dislike treating Ghostscript as source of multiple libraries! I prefer having each upstream

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-24 Thread Jonas Smedegaard
On Mon, Jan 24, 2011 at 09:29:26PM +0100, Till Kamppeter wrote: On 01/24/2011 08:47 PM, Jonas Smedegaard wrote: I think that a) ijs package should cherry-pick from ghostscript sources (manually, from upstream tarballs and/or VCS), and b) ijs package maintainers (or anyone, really - perhaps

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-24 Thread Till Kamppeter
On 01/24/2011 10:11 PM, Jonas Smedegaard wrote: Filing a bugreport also helps in resolving if perhaps ijs package maintainer might be MIA... According to http://packages.debian.org/changelogs/pool/main/i/ijs/ijs_0.35-7/changelog last change on package in April 2009, last change on active

Re: Provide libijs packages as a binary package of Ghostscript?

2011-01-24 Thread Jonas Smedegaard
On Mon, Jan 24, 2011 at 10:20:59PM +0100, Till Kamppeter wrote: On 01/24/2011 10:11 PM, Jonas Smedegaard wrote: Filing a bugreport also helps in resolving if perhaps ijs package maintainer might be MIA... According to http://packages.debian.org/changelogs/pool/main/i/ijs/ijs_0.35-7/changelog