Hi Julien,
this '#' is there in openSUSE 11.1 so I kept it. Cannot judge why this would 
be required or not.

Maybe a part of my patch must be "deopensuseified" ;-)

What regards the .desc-files: I compared the effort of creating a parser, 
reading in the desc-files and so on and so forth with a simple header 
containing maybe 10 entries if at all.

Whoever is capable of doing this effort - finding the right place within the 
desc - files and adding those data can do, I do not think that it is worth 
the time for a decreasing number of SCSI-Scanners out in the wild - though 
you are right that it should be there from a consistency standpoint.

Thanks for the inputs,
take care



Dieter


-- 
-----------------------------------------------------------

                               |
                                \
                 /\_/\           |
                | ~x~ |/-----\   /
                 \   /-       \_/
  ^^__   _        /  _  ____   /
 <??__ \- \_/     |  |/    |  |
  ||  ||         _| _|    _| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
-----------------------------------------------------------Am Donnerstag, 8. 
Januar 2009 17:41:33 schrieb Julien BLACHE:
> Re: [sane-devel] SCSI-scanners and HAL / patch for sane-desc.c
> Von:
> Julien BLACHE <jb at jblache.org>
>   An:
> Dieter Jurzitza <dieter.jurzitza at t-online.de>
>   Kopie:
> sane-devel at lists.alioth.debian.org
>   Datum:
> Heute 17:41:33
>   ?
> Dieter Jurzitza <dieter.jurzitza at t-online.de> wrote:
>
> Hi,
>
> > @@ -3180,9 +3196,10 @@
> > ?
> > ? ?print_udev_header ();
> > ? ?printf("ACTION!=\"add\", GOTO=\"libsane_rules_end\"\n"
> > -????? "ENV{DEVTYPE}==\"usb_device\", GOTO=\"libsane_create_usb_dev\"\n"
> > -????? "SUBSYSTEM==\"usb_device\", GOTO=\"libsane_rules_begin\"\n"
> > -????? "SUBSYSTEM!=\"usb_device\", GOTO=\"libsane_rules_end\"\n"
> > +????? "# ENV{DEVTYPE}==\"usb_device\",
> > GOTO=\"libsane_create_usb_dev\"\n"
>
> ? ? ? ? ? ^^^^^
>
> You broke something.
******

Reply via email to