http://bugzilla.novell.com/show_bug.cgi?id=514994
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=514994#c11
--- Comment #11 from Johannes Meixner 2009-09-17 07:43:32 MDT ---
The move to CUPS-only support in Gutenprint
will break LPRng support in Gutenprint.
LPRng is dropped in openSUSE 11.2 so that we do not need
to worry about LPRng support in 11.2 and later products.
For older products (i.e. all before openSUSE 11.2)
the new gutenprint package will not work if LPRng
or whatever other non-CUPS spooler (or no spooler at all)
is used on a particular user's system.
Regrading LPRng in general:
Some time ago (to find out if dropping LPRng could make sense)
I asked on our opensuse and opensuse-de lists to find out
if LPRng is still used, see
http://lists.opensuse.org/opensuse/2007-11/msg01723.html
and
http://lists.opensuse.org/opensuse-de/2007-11/msg00967.html
There was no response at all on the opensuse list
and little response on opensuse-de but nobody said
that it would be impossible for him to switch to CUPS.
The advantage of a move to CUPS-only support in Gutenprint is
that it removes possible but unneccessary maintenance load
because I would not have to fix bugs in the non-CUPS parts
of Gutenprint.
Such bugs are even more likely because the non-CUPS parts
of Gutenprint are probably almost totally untested because
almost nobody actually uses non-CUPS parts of Gutenprint
(neither do I) and I have a particular feeling how much
the non-CUPS parts of Gutenprint are used by the upstream
authors ;-)
Imagine a security bug in /usr/bin/ijsgutenprint
which I must fix regardless how many users actually use it
e.g. a possible exploit just because /usr/bin/ijsgutenprint
is installed and executable.
Note that I only talk about our official gutenprint package.
Of course anybody who likes can provide Gutenprint
with Foomatic and IJS Ghostscript driver support
via the openSUSE build service.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.