Feature changed by: Johannes Meixner (jsmeix) Feature #305345, revision 5 Title: Replace cups-autoconfig with hal-cups-utils openSUSE-11.2: New Priority Requester: Important Requested by: Vincent Untz (vuntz) Description: In openSUSE, we use cups-autoconfig to automatically configure new printers detected by HAL. However, no other distro uses this, and hal- cups-utils seems to be the long-term solution. Switching to hal-cups- utils means easier maintenance for us. hal-cups-utils also ships the hal backend for cups that we have in cups- backends. I've packaged a new cups-backends package (without the hal backend) and a hal-cups-utils package (with the hal backend, patched like what we had in cups-backends) in home:vuntz:factory-playground. So it's all ready for testing. Note: yast2-printer makes it possible to edit /etc/cups-autoconfig. conf. We might want to keep the configuration option of /etc/cups- autoconfig.conf in hal-cups-utils. + Discussion: + #1: Johannes Meixner (jsmeix) (2009-03-27 10:03:43) + This one looks like a duplicate of FATE#305772 -- openSUSE Feature: https://features.opensuse.org/305345

Feature changed by: Vincent Untz (vuntz) Feature #305345, revision 9 Title: Replace cups-autoconfig with hal-cups-utils openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Vincent Untz (vuntz) Description: In openSUSE, we use cups-autoconfig to automatically configure new printers detected by HAL. However, no other distro uses this, and hal- cups-utils seems to be the long-term solution. Switching to hal-cups- utils means easier maintenance for us. hal-cups-utils also ships the hal backend for cups that we have in cups- backends. I've packaged a new cups-backends package (without the hal backend) and a hal-cups-utils package (with the hal backend, patched like what we had in cups-backends) in home:vuntz:factory-playground. So it's all ready for testing. Note: yast2-printer makes it possible to edit /etc/cups-autoconfig. conf. We might want to keep the configuration option of /etc/cups- autoconfig.conf in hal-cups-utils. Discussion: #1: Johannes Meixner (jsmeix) (2009-03-27 10:03:43) This one looks like a duplicate of FATE#305772 #2: Michael Löffler (michl19) (2009-06-05 14:46:45) Vinc, it looks like or it is? Please verify. Thanks + #3: Vincent Untz (vuntz) (2009-06-05 14:54:32) (reply to #2) + 305772 has been closed as duplicate of this one already :-) -- openSUSE Feature: https://features.opensuse.org/305345

Feature changed by: Johannes Meixner (jsmeix) Feature #305345, revision 11 Title: Replace cups-autoconfig with hal-cups-utils openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Vincent Untz (vuntz) Description: In openSUSE, we use cups-autoconfig to automatically configure new printers detected by HAL. However, no other distro uses this, and hal- cups-utils seems to be the long-term solution. Switching to hal-cups- utils means easier maintenance for us. hal-cups-utils also ships the hal backend for cups that we have in cups- backends. I've packaged a new cups-backends package (without the hal backend) and a hal-cups-utils package (with the hal backend, patched like what we had in cups-backends) in home:vuntz:factory-playground. So it's all ready for testing. Note: yast2-printer makes it possible to edit /etc/cups-autoconfig. conf. We might want to keep the configuration option of /etc/cups- autoconfig.conf in hal-cups-utils. Discussion: #1: Johannes Meixner (jsmeix) (2009-03-27 10:03:43) This one looks like a duplicate of FATE#305772 #2: Michael Löffler (michl19) (2009-06-05 14:46:45) Vinc, it looks like or it is? Please verify. Thanks #3: Vincent Untz (vuntz) (2009-06-05 14:54:32) (reply to #2) 305772 has been closed as duplicate of this one already :-) #4: Stephan Kulow (coolo) (2009-06-24 13:50:35) as the mail for the maintainer of cups-autoconf bounces, I suggest we go ahead. Johannes, any problem you see? + #5: Johannes Meixner (jsmeix) (2009-06-24 15:01:00) + I alrerady wrote some mails to Vincent and Chris:In particular:-------------------------------------------------------------------------------------- + Date: Thu, 30 Apr 2009 12:34:44 +0200 (CEST)...currently I have no time + for this.I will respond in more detail when time permits.In the + meantime you may discuss it with Chris ...who knows about reasons why + we do not want a "hal" backendand how a printer autoconfig tool must be + designed to workin compliance with CUPS (in particular a printer + autoconfig toolmust use only existing well known backends like "usb" + and "hp").-------------------------------------------------------------------------------------- + Why we do not want a "hal" backend + seehttp://code.google.com/p/cups-autoconfig/"Removal of the HAL backend + from cups-backends" + -------------------------------------------------------------------------------------- + Date: Thu, 23 Oct 2008 07:20:57 +0200 (CEST)...On Oct 21 09:34 Chris + ... wrote (shortened):> On Tue, Oct 21, 2008 at 9:20 AM, Vincent ... + wrote:> > > hal-cups-utils has no configuration....> > ... I was + wondering if it's useful to> > have option for cups-autoconfig. I guess + it makes sense to lock down> > stuff, but I'm not 100% sure it's really + needed by people ...> > > The configuration options for cups-autoconfig + aren't that useful. The only,> somewhat, useful option is to disable + auto-configuration all together. I> don't think anyone would want auto- + configuration disabled unless it's not> working correctly.If the new + auto-configuration stuff is in the hal-cups-utils RPMbut there is no + configuration setting to disable it, the user candisable auto- + configuration only by removing hal-cups-utils.But if the hal backend is + part of the hal-cups-utils RPMthe user cannot remove the hal-cups-utils + RPM when thereexists at least one queue which uses the hal backend. + Therefore I recommend to have the auto-configuration stuffwell + separated from whatever else functionality.I suggest to have the auto- + configuration stuff in aRPM sub-package hal-cups-utils-autoconfig which + requiresand supplements hal-cups-utils (but hal-cups-utils mustnot + require hal-cups-utils-autoconfig).Then hal-cups-utils-autoconfig would + be installed whenhal-cups-utils is installed (because of the + supplements)and the user can install or remove hal-cups-utils- + autoconfigat any time as he likes to enable or disable auto- + configuration.Just as it works now for sane-backends-autoconfig. + Currently I don't know what our package installation magicwould do if + both hal-cups-utils-autoconfig and cups-autoconfigsupplement cups + because the two autoconfig packages conflict.-------------------------------------------------------------------------------------- -- openSUSE Feature: https://features.opensuse.org/305345

Feature changed by: Johannes Meixner (jsmeix) Feature #305345, revision 13 Title: Replace cups-autoconfig with hal-cups-utils openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Vincent Untz (vuntz) Description: In openSUSE, we use cups-autoconfig to automatically configure new printers detected by HAL. However, no other distro uses this, and hal- cups-utils seems to be the long-term solution. Switching to hal-cups- utils means easier maintenance for us. hal-cups-utils also ships the hal backend for cups that we have in cups- backends. I've packaged a new cups-backends package (without the hal backend) and a hal-cups-utils package (with the hal backend, patched like what we had in cups-backends) in home:vuntz:factory-playground. So it's all ready for testing. Note: yast2-printer makes it possible to edit /etc/cups-autoconfig. conf. We might want to keep the configuration option of /etc/cups- autoconfig.conf in hal-cups-utils. Discussion: #1: Johannes Meixner (jsmeix) (2009-03-27 10:03:43) This one looks like a duplicate of FATE#305772 #2: Michael Löffler (michl19) (2009-06-05 14:46:45) Vinc, it looks like or it is? Please verify. Thanks #3: Vincent Untz (vuntz) (2009-06-05 14:54:32) (reply to #2) 305772 has been closed as duplicate of this one already :-) #4: Stephan Kulow (coolo) (2009-06-24 13:50:35) as the mail for the maintainer of cups-autoconf bounces, I suggest we go ahead. Johannes, any problem you see? + #7: Johannes Meixner (jsmeix) (2009-07-02 14:30:09) (reply to #4) + Another try to submit my comment now using /opt/kde3/bin/fate and + explicite HTML tags to enforce paragraphs and line breaks. + I alrerady wrote some mails to Vincent and Chris: + In particular: + ------------------------------------------------------------------------ + Date: Thu, 30 Apr 2009 12:34:44 +0200 (CEST) + ... + currently I have no time for this. + I will respond in more detail when time permits. + In the meantime you may discuss it with Chris ... who knows + about reasons why we do not want a "hal" backend and + how a printer autoconfig tool must be designed to work + in compliance with CUPS (in particular a printer autoconfig + tool must use only existing well known backends like "usb" + and "hp"). + ------------------------------------------------------------------------ + Why we do not want a "hal" backend see + http://code.google.com/p/cups-autoconfig/ + "Removal of the HAL backend from cups-backends" + ------------------------------------------------------------------------ + Date: Thu, 23 Oct 2008 07:20:57 +0200 (CEST) + ... + On Oct 21 09:34 Chris ... wrote (shortened): + On Tue, Oct 21, 2008 at 9:20 AM, Vincent ... wrote: + hal-cups-utils has no configuration.... + ... I was wondering if it's useful to have option + for cups-autoconfig. I guess it makes sense + to lock down stuff, but I'm not 100% sure it's really + needed by people ... + The configuration options for cups-autoconfig aren't + that useful. The only, somewhat, useful option is + to disable auto-configuration all together. I don't + think anyone would want auto-configuration disabled + unless it's not working correctly. + If the new auto-configuration stuff is in the + hal-cups-utils RPM but there is no configuration + setting to disable it, the user can disable + auto-configuration only by removing hal-cups-utils. + But if the hal backend is part of the hal-cups-utils RPM + the user cannot remove the hal-cups-utils RPM when there + exists at least one queue which uses the hal backend. + Therefore I recommend to have the auto-configuration stuff + well separated from whatever else functionality. + I suggest to have the auto-configuration stuff in a RPM + sub-package hal-cups-utils-autoconfig which + requires and supplements hal-cups-utils (but hal-cups-utils + must not require hal-cups-utils-autoconfig). + Then hal-cups-utils-autoconfig would be installed when + hal-cups-utils is installed (because of the supplements) + and the user can install or remove hal-cups-utils-autoconfig + at any time as he likes to enable or disable auto-configuration. + Just as it works now for sane-backends-autoconfig. + Currently I don't know what our package installation magic + would do if both hal-cups-utils-autoconfig and cups-autoconfig + supplement cups because the two autoconfig packages + conflict. + ------------------------------------------------------------------------ #5: Johannes Meixner (jsmeix) (2009-06-24 15:01:00) I alrerady wrote some mails to Vincent and Chris:In particular:-------------------------------------------------------------------------------------- Date: Thu, 30 Apr 2009 12:34:44 +0200 (CEST)...currently I have no time for this.I will respond in more detail when time permits.In the meantime you may discuss it with Chris ...who knows about reasons why we do not want a "hal" backendand how a printer autoconfig tool must be designed to workin compliance with CUPS (in particular a printer autoconfig toolmust use only existing well known backends like "usb" and "hp").-------------------------------------------------------------------------------------- Why we do not want a "hal" backend seehttp://code.google.com/p/cups-autoconfig/"Removal of the HAL backend from cups-backends" -------------------------------------------------------------------------------------- Date: Thu, 23 Oct 2008 07:20:57 +0200 (CEST)...On Oct 21 09:34 Chris ... wrote (shortened):> On Tue, Oct 21, 2008 at 9:20 AM, Vincent ... wrote:> > > hal-cups-utils has no configuration....> > ... I was wondering if it's useful to> > have option for cups-autoconfig. I guess it makes sense to lock down> > stuff, but I'm not 100% sure it's really needed by people ...> > > The configuration options for cups-autoconfig aren't that useful. The only,> somewhat, useful option is to disable auto-configuration all together. I> don't think anyone would want auto- configuration disabled unless it's not> working correctly.If the new auto-configuration stuff is in the hal-cups-utils RPMbut there is no configuration setting to disable it, the user candisable auto- configuration only by removing hal-cups-utils.But if the hal backend is part of the hal-cups-utils RPMthe user cannot remove the hal-cups-utils RPM when thereexists at least one queue which uses the hal backend. Therefore I recommend to have the auto-configuration stuffwell separated from whatever else functionality.I suggest to have the auto- configuration stuff in aRPM sub-package hal-cups-utils-autoconfig which requiresand supplements hal-cups-utils (but hal-cups-utils mustnot require hal-cups-utils-autoconfig).Then hal-cups-utils-autoconfig would be installed whenhal-cups-utils is installed (because of the supplements)and the user can install or remove hal-cups-utils- autoconfigat any time as he likes to enable or disable auto- configuration.Just as it works now for sane-backends-autoconfig. Currently I don't know what our package installation magicwould do if both hal-cups-utils-autoconfig and cups-autoconfigsupplement cups because the two autoconfig packages conflict.-------------------------------------------------------------------------------------- #6: Johannes Meixner (jsmeix) (2009-06-24 15:03:58) (reply to #5) Seems the web interface is broken because I selected explicitely "preformatted" for my above comment(and I had CR/LF therein).... -- openSUSE Feature: https://features.opensuse.org/305345

Feature changed by: Stephan Kulow (coolo) Feature #305345, revision 15 Title: Drop cups-autoconfig (replaced by udev helpers in system-config- printer) - openSUSE-11.2: Evaluation + openSUSE-11.2: Done Priority Requester: Important Projectmanager: Important Requested by: Vincent Untz (vuntz) Description: In openSUSE, we use cups-autoconfig to automatically configure new printers detected by HAL. However, no other distro uses this, and hal- cups-utils seems to be the long-term solution. Switching to hal-cups- utils means easier maintenance for us. hal-cups-utils also ships the hal backend for cups that we have in cups- backends. I've packaged a new cups-backends package (without the hal backend) and a hal-cups-utils package (with the hal backend, patched like what we had in cups-backends) in home:vuntz:factory-playground. So it's all ready for testing. Note: yast2-printer makes it possible to edit /etc/cups-autoconfig. conf. We might want to keep the configuration option of /etc/cups- autoconfig.conf in hal-cups-utils. Discussion: #1: Johannes Meixner (jsmeix) (2009-03-27 10:03:43) This one looks like a duplicate of FATE#305772 #2: Michael Löffler (michl19) (2009-06-05 14:46:45) Vinc, it looks like or it is? Please verify. Thanks #3: Vincent Untz (vuntz) (2009-06-05 14:54:32) (reply to #2) 305772 has been closed as duplicate of this one already :-) #4: Stephan Kulow (coolo) (2009-06-24 13:50:35) as the mail for the maintainer of cups-autoconf bounces, I suggest we go ahead. Johannes, any problem you see? #7: Johannes Meixner (jsmeix) (2009-07-02 14:30:09) (reply to #4) Another try to submit my comment now using /opt/kde3/bin/fate and explicite HTML tags to enforce paragraphs and line breaks. I alrerady wrote some mails to Vincent and Chris: In particular: ------------------------------------------------------------------------ Date: Thu, 30 Apr 2009 12:34:44 +0200 (CEST) ... currently I have no time for this. I will respond in more detail when time permits. In the meantime you may discuss it with Chris ... who knows about reasons why we do not want a "hal" backend and how a printer autoconfig tool must be designed to work in compliance with CUPS (in particular a printer autoconfig tool must use only existing well known backends like "usb" and "hp"). ------------------------------------------------------------------------ Why we do not want a "hal" backend see http://code.google.com/p/cups-autoconfig/ "Removal of the HAL backend from cups-backends" ------------------------------------------------------------------------ Date: Thu, 23 Oct 2008 07:20:57 +0200 (CEST) ... On Oct 21 09:34 Chris ... wrote (shortened): On Tue, Oct 21, 2008 at 9:20 AM, Vincent ... wrote: hal-cups-utils has no configuration.... ... I was wondering if it's useful to have option for cups-autoconfig. I guess it makes sense to lock down stuff, but I'm not 100% sure it's really needed by people ... The configuration options for cups-autoconfig aren't that useful. The only, somewhat, useful option is to disable auto-configuration all together. I don't think anyone would want auto-configuration disabled unless it's not working correctly. If the new auto-configuration stuff is in the hal-cups-utils RPM but there is no configuration setting to disable it, the user can disable auto-configuration only by removing hal-cups-utils. But if the hal backend is part of the hal-cups-utils RPM the user cannot remove the hal-cups-utils RPM when there exists at least one queue which uses the hal backend. Therefore I recommend to have the auto-configuration stuff well separated from whatever else functionality. I suggest to have the auto-configuration stuff in a RPM sub-package hal-cups-utils-autoconfig which requires and supplements hal-cups-utils (but hal-cups-utils must not require hal-cups-utils-autoconfig). Then hal-cups-utils-autoconfig would be installed when hal-cups-utils is installed (because of the supplements) and the user can install or remove hal-cups-utils-autoconfig at any time as he likes to enable or disable auto-configuration. Just as it works now for sane-backends-autoconfig. Currently I don't know what our package installation magic would do if both hal-cups-utils-autoconfig and cups-autoconfig supplement cups because the two autoconfig packages conflict. ------------------------------------------------------------------------ #5: Johannes Meixner (jsmeix) (2009-06-24 15:01:00) I alrerady wrote some mails to Vincent and Chris:In particular:-------------------------------------------------------------------------------------- Date: Thu, 30 Apr 2009 12:34:44 +0200 (CEST)...currently I have no time for this.I will respond in more detail when time permits.In the meantime you may discuss it with Chris ...who knows about reasons why we do not want a "hal" backendand how a printer autoconfig tool must be designed to workin compliance with CUPS (in particular a printer autoconfig toolmust use only existing well known backends like "usb" and "hp").-------------------------------------------------------------------------------------- Why we do not want a "hal" backend seehttp://code.google.com/p/cups-autoconfig/"Removal of the HAL backend from cups-backends" -------------------------------------------------------------------------------------- Date: Thu, 23 Oct 2008 07:20:57 +0200 (CEST)...On Oct 21 09:34 Chris ... wrote (shortened):> On Tue, Oct 21, 2008 at 9:20 AM, Vincent ... wrote:> > > hal-cups-utils has no configuration....> > ... I was wondering if it's useful to> > have option for cups-autoconfig. I guess it makes sense to lock down> > stuff, but I'm not 100% sure it's really needed by people ...> > > The configuration options for cups-autoconfig aren't that useful. The only,> somewhat, useful option is to disable auto-configuration all together. I> don't think anyone would want auto- configuration disabled unless it's not> working correctly.If the new auto-configuration stuff is in the hal-cups-utils RPMbut there is no configuration setting to disable it, the user candisable auto- configuration only by removing hal-cups-utils.But if the hal backend is part of the hal-cups-utils RPMthe user cannot remove the hal-cups-utils RPM when thereexists at least one queue which uses the hal backend. Therefore I recommend to have the auto-configuration stuffwell separated from whatever else functionality.I suggest to have the auto- configuration stuff in aRPM sub-package hal-cups-utils-autoconfig which requiresand supplements hal-cups-utils (but hal-cups-utils mustnot require hal-cups-utils-autoconfig).Then hal-cups-utils-autoconfig would be installed whenhal-cups-utils is installed (because of the supplements)and the user can install or remove hal-cups-utils- autoconfigat any time as he likes to enable or disable auto- configuration.Just as it works now for sane-backends-autoconfig. Currently I don't know what our package installation magicwould do if both hal-cups-utils-autoconfig and cups-autoconfigsupplement cups because the two autoconfig packages conflict.-------------------------------------------------------------------------------------- #6: Johannes Meixner (jsmeix) (2009-06-24 15:03:58) (reply to #5) Seems the web interface is broken because I selected explicitely "preformatted" for my above comment(and I had CR/LF therein).... #8: Vincent Untz (vuntz) (2009-07-23 20:32:12) Note: latest system-config-printer will come with some udev-based tools that will replace hal-cups-utils. Need to investigate that. + #9: Stephan Kulow (coolo) (2009-09-07 13:51:46) (reply to #8) + rq20047 drops cups-autoconfig - it's already dropped from DVD. -- openSUSE Feature: https://features.opensuse.org/305345