https://bugzilla.novell.com/show_bug.cgi?id=276905 kssingvo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #1 from kssingvo@novell.com 2007-05-22 04:34 MST ------- I don't have the feeling thats it's up to you to decide which version we want to include into the distribution or not. We want to have a stable version and not a development release. Thanks for understanding. ==> INVALID Please use your own branch of openSUSE build service, if you need any modified packages for critical usability. Thanks for understanding. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=276905 ------- Comment #3 from kssingvo@novell.com 2007-06-04 02:18 MST ------- As said before: I don't to want to have any unstable and half-baken drivers in our distribution. And as a result, the development version of gutenprint was updated on Saturday (2007-JUN-02 / new version: 5.1.2). Some major bugs got fixed. Your suggestion was doubtful. Yes, I'm reading software announcements of all printer projects which our distribution already contains. Cite of the Changes of 5.1.2: Changes: This release fixes a number of problems in 5.1.1 including new Epson printers not printing black, the Postscript driver always printing grayscale, printing CDs correctly in all cases on Epson printers, and borderless printing working correctly on a number of Epson multi-function devices. In addition, Epson printers using Claria ink have been retuned for improved quality. If customers are unhappy with support of Epson printers, please lets first start discussing who is ignoring the OpenSource world: Epson or SuSE. As a counter-example have a look at HP and their hplip (hpinket) project at SourceForge: nearly all of their printers are support by it. This excellent support of their own printers is done by HP itself since many, many years. So HP showed that it is possible to provide (real) OpenSource drivers by the vendor himself. Epson (and others) instead are showing an ongoing ignorance of the OpenSource world. And as HP is working together with the distributions, they are in the OpenSource world many steps ahead before other vendors. I would suggest to rethink about the current situation: about which vendors are supporting OpenSource and which are not. And then let all the printers vendors show by your money (buying behavior) if you want to get OpenSource drivers or not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=276905 ------- Comment #5 from kssingvo@novell.com 2007-06-05 02:57 MST ------- Well, the past showed, if the vendors don't move regarding opening the specs or writing OpenSource drivers, we had to point this out. You name this crusade, and I don't have any better word for this, but don't like crusade neither. But it showed, this "crusade" was so far the only working way to make enough pressure on the vendors to get them moved. About the YaST printer modules. FYI: the database is a hash of existing printer drivers. If you read about a "rebuild" its in reality a rescan of existing files (several thousands). And this is comparison is mandatory necessary. We had to many problematic scenarios, when only comparing time-stamps or similar is done. The IP detection via scanning the networks got noticed on very high secure machines too, and it was considered as a break-in attempt on those. So we had to remove this functionality. Yes, I'm unhappy with the GUI to call cupsenable (10.2+) or enable (10.1 and before) in the YaST module too. We want to change this for next distribution in a better. Let's see, if it can be done in time. But in the meantime the backend "beh" might help you, if you notice this to often. We are aware of those drivers, and have already included pipslite (in 10.2 first time, as it wasn't avail before). But the backdraw of some of the other drivers is, that the main raster function is shipped in a binary library only. This means we cannot use it on all of our supported architectures (ppc, ppc64, s390, s390x, nor x86_64/AMD64/EM64T), nor can we write/build security updates to our standards if necessary, nor can be shipped if our linker changes to much, nor can build/derive one library for all supported printers. At the moment the packages Epson/Avasys provides, a customer who posses two different supported printers must decide which of the equal named shared library he wants to install, and can never install both printers. I'm quiet unhappy about this solution Epson/Avasys provides at the moment. Your overview of the quality of the gimp-print drivers is true for the devel version. But still I got the feeling that the non-devel tree is a bit more stable then the devel tree. Keep in mind, we have to provide printer drivers for customers with old Epson printers too, even this seems not to be your case. If you want to provide your customers the devel version, you can use our openSUSE build service to derive from existend cups-drivers package and included their your preferred version of gutenprint. This can be done very easily. But building Security Updates for your customers is up to you then. I still would rethink if don't consider to your customers selling those Epson printers and buying HP. Live would be much easier then. We already told our concerns (see above) regarding the driver situation to Epson/Avasys. But as you already said, the culture is different, and I think we spoke too frankly, to constructive, or whatever. The contact died short after it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.