Hi Anyone know why opensuse is 3 releases behind in Cups. I'm still on 1.5.4 and there's been 1.6 and 1.7 releases and now 2.0 is in the wild. I'm guessing that 1.6 and 1.7 were deemed to add no value. regards Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Sonntag, 19. Oktober 2014, 19:31:57 schrieb ianseeks:
Hi
Anyone know why opensuse is 3 releases behind in Cups. I'm still on 1.5.4 and there's been 1.6 and 1.7 releases and now 2.0 is in the wild.
I'm guessing that 1.6 and 1.7 were deemed to add no value.
regards
Ian You will find some explanation on https://en.opensuse.org/Portal:Printing -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Sonntag, 19. Oktober 2014, 19:31:57 schrieb ianseeks:
Hi
Anyone know why opensuse is 3 releases behind in Cups. I'm still on 1.5.4 and there's been 1.6 and 1.7 releases and now 2.0 is in the wild.
I'm guessing that 1.6 and 1.7 were deemed to add no value.
regards
Ian
You will find some explanation on https://en.opensuse.org/Portal:Printing
On Sunday 19 Oct 2014 20:41:31 Markus Koßmann wrote: thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-19 20:53, ianseeks wrote:
On Sunday 19 Oct 2014 20:41:31 Markus Koßmann wrote:
Am Sonntag, 19. Oktober 2014, 19:31:57 schrieb ianseeks:
You will find some explanation on https://en.opensuse.org/Portal:Printing thanks
In particular this: https://bugzilla.novell.com/show_bug.cgi?id=735404 The number of issues is huge... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlREE+0ACgkQtTMYHG2NR9U2OwCePF93/4PbCaBoqpP5RNemhZvJ NpIAn3ufDPx8b57UihC4Rrp0ve8e1MBi =Rpki -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On October 19, 2014 12:41:35 PM PDT, "Carlos E. R."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-19 20:53, ianseeks wrote:
On Sunday 19 Oct 2014 20:41:31 Markus Koßmann wrote:
Am Sonntag, 19. Oktober 2014, 19:31:57 schrieb ianseeks:
You will find some explanation on https://en.opensuse.org/Portal:Printing thanks
In particular this: https://bugzilla.novell.com/show_bug.cgi?id=735404
The number of issues is huge...
- --
On the other hand, what we are running isn't broke, so no rush to fix it. If Apple is going to gut the thing, maybe we should wait and see. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-19 23:39, John Andersen wrote:
On October 19, 2014 12:41:35 PM PDT, "Carlos E. R." <> wrote:
In particular this: https://bugzilla.novell.com/show_bug.cgi?id=735404
The number of issues is huge...
On the other hand, what we are running isn't broke, so no rush to fix it.
If Apple is going to gut the thing, maybe we should wait and see.
It will stop working sooner or later. So all distributions will have to find an alternative or take themselves the support and development. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlREOTIACgkQtTMYHG2NR9VoiACfV8tr+JMAJyRXj/PIUWJLTsJ6 VmAAn38hM19OhOd+uw9nsb9pvN+OT9FR =+UkR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/19/2014 03:20 PM, Carlos E. R. wrote:
On the other hand, what we are running isn't broke, so no rush to
fix it.
If Apple is going to gut the thing, maybe we should wait and see. It will stop working sooner or later. So all distributions will have to find an alternative or take themselves the support and development.
-- Cheers / Saludos,
Well the sooner that starts the sooner it will be taken care of. This problem has been known since 2012, when Apple told everybody they were going to drop almost everything that isn't use in OSX and let the Linux world fend for themselves. http://www.unixmen.com/201202-apple-orphans-linux-cups-features-handicaps-op... Apple is at best a reluctant open source player, that can be dragged kicking and screaming to opensource if the threat of lawyers is raised. There is no reason code has to "break sooner of later". In my day job maintain entire systems that were written when Jimmy Carter was in office (1977). It has been re-platformed three times over the years. But original code still runs. - -- Explain again the part about rm -rf / -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlREQSwACgkQv7M3G5+2DLI5JQCfRMDRnyokg5lmecu2Yl5l++ng zhYAni50NBX360ISvRlR8THyH1960h7w =xyHa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Oct 19, 2014 at 6:54 PM, John Andersen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/19/2014 03:20 PM, Carlos E. R. wrote:
On the other hand, what we are running isn't broke, so no rush to
fix it.
If Apple is going to gut the thing, maybe we should wait and see. It will stop working sooner or later. So all distributions will have to find an alternative or take themselves the support and development.
-- Cheers / Saludos,
Well the sooner that starts the sooner it will be taken care of.
This problem has been known since 2012, when Apple told everybody they were going to drop almost everything that isn't use in OSX and let the Linux world fend for themselves. http://www.unixmen.com/201202-apple-orphans-linux-cups-features-handicaps-op...
Apple is at best a reluctant open source player, that can be dragged kicking and screaming to opensource if the threat of lawyers is raised.
There is no reason code has to "break sooner of later". In my day job maintain entire systems that were written when Jimmy Carter was in office (1977). It has been re-platformed three times over the years. But original code still runs.
- -- Explain again the part about rm -rf / -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlREQSwACgkQv7M3G5+2DLI5JQCfRMDRnyokg5lmecu2Yl5l++ng zhYAni50NBX360ISvRlR8THyH1960h7w =xyHa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It sounds like it is time to launch a CUPS fork before this becomes a major issue in the future. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25 October 2014 20:32, Timothy Butterworth
It sounds like it is time to launch a CUPS fork before this becomes a major issue in the future.
The Red Hat ringing guys have a contingency plan in place (google for printerd), basically it would replace the spooling component of CUPS with a new daemon, but maintain the printer driver compatibility with CUPS, as that's the really hard part and where we need Apple's market leverage. There is a lot of legacy code and api in CUPS which is better removed, but we don't want to fork until we absolutely have to as it is a lot of work, there are few experts in this area, and even fewer companies willing to pay people to work on it full time. John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2014-10-19 at 15:54 -0700, John Andersen wrote:
On 10/19/2014 03:20 PM, Carlos E. R. wrote:
There is no reason code has to "break sooner of later". In my day job maintain entire systems that were written when Jimmy Carter was in office (1977). It has been re-platformed three times over the years. But original code still runs.
There are two reasons for that "breaking". One, is that the software components around change. APIs change, library calls, things. And you have to redesign parts of your code so that it still builds and runs. The other, is that CUPs has to talk with hardware, and hardware does change. New printers appears on the market, and people expect them to work. We do need those new drivers. Who is to make them? The contingency plan is to just port the new drivers from upstream cups, as needed. Then CUPS does have many unsolved issues... Linux is wining battles, but it is also loosing them. Launch a fork? Sure. Who is going to do it? Where is the manpower? - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRMMaYACgkQtTMYHG2NR9VPOwCfW0+9/69pTNy0lWMI5XvkHBS+ W+UAn1H+b3SCCcTfwgIRv9uyOvwGZ+4g =Ivxn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carlos E. R. -
ianseeks -
John Andersen -
John Layt -
Markus Koßmann -
Timothy Butterworth