Hi, these are unified ebuilds (idealy) supporting all brother printers with linux drivers. The ebuilds have been tested with a Brother DCP-J925WD, other printers *should* work, but are untested. Feedback is of course welcome. I also wrote a python script to automatically generate both ebuilds to make updates easier. Please add them to the portage tree. Best regards, Fabian Henze Reproducible: Always
Created attachment 299633 [details] brother-lpr-driver-20120123.ebuild
Created attachment 299635 [details] brother-cupswrapper-20120123.ebuild
Created attachment 299637 [details] generateBrotherEbuilds.py btw. I am unsure if this should really be fetch-restricted. What is the policy on this?
Tested the ebuild with an Brother HL-2070N and it worked splendidly. emerged both cupswrapper and lpr. Afterwards the Printer was listed in CUPS ready to be added.
*** This bug has been marked as a duplicate of bug 355555 ***
hi, i try to use your ebuild on my ~amd64 gentoo but when i try to make the manifest i got the folowing message: !!! /home/adamaru/projets/portage-overlay/lpr/cupswrapper/brother-lpr-driver-20120123.ebuild does not seem to have a valid PORTDIR structure. (portage version 2.2.0_alpha96) i'm trying to install the HL-3040CN printer and this ebuild is my last chance to do this (cups reconize my printer but send me: E [01/Apr/2012:13:48:15 +0200] Returning HTTP Forbidden for CUPS-Get-Devices (no URI) from localhost E [01/Apr/2012:13:48:15 +0200] Returning HTTP Forbidden for CUPS-Get-Devices (no URI) from localhost E [01/Apr/2012:13:48:15 +0200] Returning HTTP Forbidden for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HL3040CN) from localhost ) there is an overlay when i can found your ebuild ? thanks.
Your portage overlay has to follow portage directory and ebuild naming conventions, namely: The ebuild should follow the naming sheme "category/programname/programname-version.ebuild". In your case: /path/to/overlay/net-print/brother-lpr-driver/brother-lpr-driver-20120123.ebuild /path/to/overlay/net-print/brother-cupswrapper/brother-cupswrapper-20120123.ebuild There is no public overlay (I know of) with this ebuild, but I can send you a tarball if you continue to have problems.
i renamed the path with the good name convention, but i got this: StarK brother-cupswrapper # ebuild brother-cupswrapper-20120123.ebuild manifest !!! net-print/brother-cupswrapper-20120123 has fetch restriction turned on. !!! This probably means that this ebuild's files must be downloaded !!! manually. See the comments in the ebuild for more information. * Select 'I Accept' and move the file(s) to /usr/portage/distfiles. !!! Fetch failed for cupswrapperMFC6800-1.0.2-1.i386.deb, can't update Manifest can you make me a tarball please ? thanks
i edited the ebuild (removed the fetch restrict), the ebuild successfully downloaded all the needed files, i've put my printer on the use list, emerged the ebuild , reinstalled the printer but: i still cant print :s no error messages in the log (my printer is not on usb, it's on network but i need this network mode) they're is a thing to do ? (i launch the scripts that the ebuild told me to launch but it auto configure a printer to /dev/usb/lp0 )
I don't think your problems are related to this ebuild and this is not a support channel, so please don't spam this bug report. If you have problems using the driver contact brother support or read the documentation on http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/index.html Just a last piece of advice: Try adding the printer manually via the cups webinterface (http://localhost:631/)
Are you interested in maintaning this driver directly yourself in the new printer-drivers overlay [1]? If yes, just send me via personal e-mail at dilfridge@gentoo.org the following data, so we can give you git push access to the overlay: * the user name that you'd like to have * your public ssh key [2], so we can give you git push access to the overlay * your e-mail address * and your full name If you have a gnupg key, you should sign that e-mail [3]. Just a few rules: * Initially, the ebuilds should work for you, and not break anything else. * You enter yourself as maintainer in metadata.xml (together with the printing herd), and are then automatically cc'ed in bug reports on bugzilla. * We will guide you towards improving the ebuilds over the next months so they follow the rules and qa guidelines of the Gentoo main portage tree. In particular this means also using a recent EAPI (3 or perferably 4), and fixing repoman warnings [4]. Don't worry, we'll help you with that. * I hope this is never going to happen, but... ebuilds that "work but go against the guidelines" and do not see any improvement will be removed again one year after initial addition. There are many ways to get help. * You can directly ask me by personal e-mail (my time is limited, but I'll try), * you can ask on freenode, channel #gentoo-dev-help, * you can read the documentation (ebuild howto [5], devmanual [6]), * ... [1] http://git.overlays.gentoo.org/gitweb/?p=proj/printer-drivers.git;a=summary [2] http://www.gentoo.org/doc/en/articles/openssh-key-management-p1.xml [3] http://www.gentoo.org/doc/en/gnupg-user.xml [4] http://dev.gentoo.org/~zmedico/portage/doc/man/repoman.1.html [5] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2 [6] http://devmanual.gentoo.org/
