Hello, On Mar 26 16:51 Verner Kjærsgaard wrote (shortened):
May one ask, just out of curiousity, eh why was the Yast Printer thing rewritten from scratch? To me, it worked just fine?
You lucky one! The old yast2-printer had become over many years an unmaintainable mess of convoluted code ("many" regarding Linux development speed, not regarding e.g. development speed of mankind or the universe). We got more and more almost unfixable bugs. You change the code here to fix it and somewhere else something breaks as unexpected side-effect or it took ages until the actual reason of a bug was found in the convoluted code so that the effort to actually fix a bug became terrible. This does not mean that the developers made bad code. It is just what happens over the time when a config tool which started at lprold/apsfilter times was adapted for LPRng/apsfilter and further on for LPRng/lpdfilter then to LPRng/lpdfilter+CUPS up to CUPS-only while at the same time CUPS changed also a lot. At some point the only reasonable way to get rid of outdated stuff is to actually get completely rid of it. At http://en.opensuse.org/YaST/Development/Printer_Enhancement see in particular the sections "Basic Design Ideas" and "Basic Implementation Principles" To implement such a new design, it is easiest to start from scratch because changing the old code would in the end result the same - only in a more painful way - when almost all of the old code would have to be changed it is easier to simply start from scratch. Of course a new design results new bugs. The most annoying one was https://bugzilla.novell.com/show_bug.cgi?id=468046 which is full of background information what actually happens while a print queue is set up. I.e. I mean it is interesting to read it ;-) Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex