The ptouch drivers for the Brother label printers are here: http://www.diku.dk/hjemmesider/ansatte/panic/P-touch/ I installed them like so: > tar zxf ptouch-driver-*.tar.gz > cd ptouch-driver-* > ./configure --prefix=/usr > make > make install > cd /usr/bin > ln -s /usr/lib/cups/filter/rastertoptch and they worked great once I installed foomatic-db to have the PPDs generated. It would be great to have an ebuild for the ptouch drivers. Reproducible: Always
Created attachment 235475 [details] ptouch-driver ebuild. COLLISION WARNING: this will not istall besides the current foomatic-db I Added the ebuild for this. But one can not install it, because files collide with files provided in foomatic-db. See bug 285905 for a revised foomatic-db without those files.
Thank you Nils, very kind.
Hi, I have 3 patches which I've developed when working on my own ptouch-driver ebuild. I've posted them by mistake on the foomatic-db bug: https://bugs.gentoo.org/show_bug.cgi?id=285905 It would be good to integrate them into the ptouch-driver ebuild once the foomatic-db conflict is resolved.
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/
Upstream has moved to https://bitbucket.org/philpem/printer-driver-ptouch and they have been releasing updates for quite a while. I've created an ebuild for the latest version they've released. I've also updated the current foomatic-db ebuilds so they won't conflict with the ptouch-driver ebuilds.
Created attachment 423186 [details] net-print/ptouch-driver-1.4.ebuild
Should I attach my updated foomatic-db ebuilds to this bug, or create a new one? Andreas, I am willing to be the maintainer for the ptouch-driver ebuilds. Is the email you mentioned still recent?
