Make this available via the ebuild
Created attachment 76503 [details] First Attempt at Ebuild Hopefully you will find this helpful. I wasn't sure what to make the license since it is a mix of licenses. The patches needed for this ebuild will follow.
Created attachment 76504 [details, diff] sane-dir-rename.diff Move the /usr/local/Brother/sane directory to /usr/share/sane/Brother.
Created attachment 76505 [details, diff] usb-claim.diff Fixes a bug in the code where it would claim a USB device before setting a configuration. Linux kernel 2.6.13 and above now enforces.
Would be nice to automatically modify the dll.conf (rather easy) and to get rid of the hardcoded version numbers in the ebuild. Mix of which licenses?
It's a mix of the LGPL, Brother's Open Source License, and Brother's Binary License. An ebuild shouldn't modify a another package's configuration file on install. Maybe add it to a pkg_config section but it seemed like such a small thing for a configuration section. Without knowing how they are going to number things it's hard not to have a hardcoded version number in there. I'm not even sure if 1.0.0 should be used since that's the name of the file, or 0.0.1 which is specified on their website.
(In reply to comment #5) > An ebuild shouldn't modify a another package's configuration file on install. > Maybe add it to a pkg_config section but it seemed like such a small thing for > a configuration section. Why do you think it shouldn't? It won't get changed unnoticed anyway since this file is config protected by default. So the user will be asked to merge the changes, and he can discard them if he wants to. Another point: Why emerge a backend that you don't want to use?
Licenses which aren't in portage yet have to be put there, and all licenses which apply should be listed in LICENSE.
Would be nice to have it in portage, but it seems Brother changed their policy on distributing the source code: "If you require, we will send you the source file based on the GPL license." They provide RPM and Debian packages only. Any ideas?
(In reply to comment #8) > Would be nice to have it in portage, but it seems Brother changed their policy > on distributing the source code: "If you require, we will send you the source > file based on the GPL license." > They provide RPM and Debian packages only. Any ideas? Ask for the source, re-package it, maintain it :-/ I am afraid this requires more than the time I could invest in this driver. Not having the hardware doesn't make it easier.
Well, I have the hardware in the company I work for and I have gentoo there as well. Got the sourcecode after some mails. Now I'm trying to make a package and then check if and how I could provide the sourcecode for download.
(In reply to comment #10) > Well, I have the hardware in the company I work for and I have gentoo there as > well. Got the sourcecode after some mails. Now I'm trying to make a package and > then check if and how I could provide the sourcecode for download. If you get it to work we could of course upload this to the gentoo mirrors, that's no problem. I just wonder if you will have to go begging for the source with each release from now on...
brscan sources are available here: http://solutions.brother.com/linux/en_us/download_src.html#2 licence is GPL2
Don't have access to that hardware anymore, un-CC myself.
