Please include this patch for brother USB scanners iwith the sane-backend package.
The patch is for sane < .13 and will need some work. Could take a while.
mr_bones: sane* is graphics@gentoo.org
Just working on adapting the patch. Nice to know that sane-backends has found some maintainers, but please update metadata.xml accordingly, then.
Seems to compile now, no idea if it works - Steven, please test and remind me to give this patch upstream if it's ok, then :-) .13-r2 should hit portage mirrors soon.
You've labeled this resolved/fixed already, but I've got a problem here: >> emerge (2 of 4) media-gfx/sane-backends-1.0.13-r2 to / *** Adjusting cvs-src permissions for portage user... >>> md5 src_uri ;-) sane-backends-1.0.13.tar.gz eutils >>> Unpacking source... >>> Unpacking sane-backends-1.0.13.tar.gz to /var/tmp/portage/sane-backends-1.0.13-r2/work >>> Unpacking sane-backends-1.0.13-brothermfc.patch.bz2 to /var/tmp/portage/sane-backends-1.0.13-r2/work bzip2: Can't open input file /usr/portage/distfiles/sane-backends-1.0.13-brothermfc.patch.bz2: No such file or directory. !!! ERROR: media-gfx/sane-backends-1.0.13-r2 failed. !!! Function unpack, Line 314, Exitcode 1 !!! failure unpacking sane-backends-1.0.13-brothermfc.patch.bz2
Thanks, this showed a different error I made.... But it should work if you put "usb" into your USE.
Please note that the patch is fetched even when you don't have a brother scanner in your SANE_BACKENDS list. I believe this is broken, since all other backends respect that variable. Shoud I file another bug report?
Please say something, or I will open another report.
patches are fetched and applied always if possible (and pushed through upstream)
(In reply to comment #7) > Please note that the patch is fetched even when you don't have a brother > scanner in your SANE_BACKENDS list. I believe this is broken, since all other > backends respect that variable. The patch is fetched, but the driver is not built if you specify something different in SANE_BACKENDS - just like any other driver. This is because the file list in SRC_URI may not depend on this variable, only the build process can and does. > Shoud I file another bug report? No, please don't do that.
I see, thanks!
