Created attachment 303945 [details] sane-backends-kodakaio-02.2.ebuild I managed to get the modified sane-backends for Kodak all-in-one devices to work, using a modified ebuild for the normal sane-backends. (Now only accepts SANE_BACKENDS="kodakaio" and nothing else.) It installs and scans fine. (Very good quality on my ESP Office 2170.) It even works when you want a scan server. The only problem is, that it should obviously be integrated into the original sane-backends upstream. (Or as a workaround, use only one ebuild, but internally switch to these sources and this behavior when SANE_BACKENDS="kodakaio" is requested. Which is easy to do, and would solve it for most end-users right now. [Only problem: What if you have multiple scanners?]) But until that is happened… (Which might take months or years :/) …this one, together with my printer ebuild, makes the Kodak AIO device *fully usable* under Gentoo! Which is awesome, considering that 24 hours ago, the thing was *not usable at all* under Gentoo. So I say, let’s put it in Portage. :)
Created attachment 303949 [details] sane-backends-kodakaio-02.2.ebuild Oh damn! I forgot, that the source file only exists on the SourceForge servers! I still had my local SRC_URI in there! Please, before putting this into Portage, set a proper value for SRC_URI. The original file is kodakaio-02.2.tar.gz found here: http://sourceforge.net/projects/cupsdriverkodak/files/Scanning%20-%20sane%20backend/ You have to run # tar -xvf kodakaio-02.2.tar.gz # cd kodakaio-02.2/ # mv ReleaseNotes-kodakaio-02.2 sane-backends-kodakaio-02.2/ # Optional # tar -cvJf sane-backends-kodakaio-02.2.tar.xz sane-backends-kodakaio-02.2 # chown portage:portage sane-backends-kodakaio-02.2.tar.xz # chmod g+w sane-backends-kodakaio-02.2.tar.xz to get the correct file. Also, I disabled the v4l backend, and all other patches, to avoid fixing the them. But it very likely probably would be possible to enable v4l again, as it’s a built-in one.
P.S.: Of course the $Header line is wrong too. ;)
Created attachment 303963 [details] sane-backends-kodakaio-02.2-r1.ebuild Improved ebuild. I put the net backend in again.
We already have a SANE_BACKENDS=kodak.
(In reply to comment #4) > We already have a SANE_BACKENDS=kodak. The current „kodak“ backend is solely for (very) old SCSI/Firewire scanners, and has nothing to do with current consumer devices. I fell for that too, but please, next time at least read up about it, OK? Of course, it I’d maintain this, I’d rename “kodak” to “kodak-old“ and “kodakaio“ to “kodak“ or “kodak-aio”, since that’s what most people assume. (As you did right now, and as I did too. It’s a trap! ^^)
Well, the way you provided it this is as dirty as it gets, and I really can't do this driver's author's work and integrate it with the upstream sources. Maybe it works fine, but this goes beyond what I am willing to support, thank you and sorry. Whoever wants to install this can use the ebuild from this bug, but it is far from good for integration into the main tree.
(In reply to comment #6) > Well, the way you provided it this is as dirty as it gets, No doubt about that. :) But it works. Which is more than “doesn’t work”. > and I really can't do this driver's author's work and integrate it with the upstream sources. Nobody expected that. There isn’t even a need. I, for example, would change my ebuild by adding the old ebuild’s code in there, and add a use flag “oldkodak” that enables it instead. (Simple if/else.) Dirty? Hell yeah! Works! Hell yeah! ^^ > Maybe it works fine, but this goes beyond what I am willing to > support, thank you and sorry. No need to say sorry. This is free software. Nobody has to do anything he doesn’t want to. And I understand why. :) > Whoever wants to install this can use the > ebuild from this bug, but it is far from good for integration into the main > tree. I’m a total ebuild n00b. I thought now that it is working, the rest would just a bit of polishing. :/ Maybe it’s best to put it in an overlay for experimental stuff, until somebody upstream uses Gentoo + buys such a printer = has a reason and the will to do it. ;) Thanks anyway.
