Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 290494

Summary: Ebuilds for Brother PT-9500PC LPR driver and CUPS wrapper.
Product: Gentoo Linux Reporter: Theo Baumgartner <tbaumgartner>
Component: Current packagesAssignee: Printing Team <printing>
Status: CONFIRMED ---    
Severity: enhancement    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on: 399875    
Bug Blocks: 399013    
Attachments: Brother PT-9500PC LPR driver ebuild.
Brother PT-9500PC CUPS wrapper ebuild.

Description Theo Baumgartner 2009-10-25 19:22:48 UTC
I've made some Ebuilds for the Brother PT-9500PC. I've used the HL-5250DN Ebuilds from Bug #208029 as templates.

I've tested them on my amd64 machine. If i've done something stupid please tell me.

Reproducible: Always
Comment 1 Theo Baumgartner 2009-10-25 19:45:38 UTC
Created attachment 208244 [details]
Brother PT-9500PC LPR driver ebuild.
Comment 2 Theo Baumgartner 2009-10-25 19:46:29 UTC
Created attachment 208246 [details]
Brother PT-9500PC CUPS wrapper ebuild.
Comment 3 Andreas K. Hüttel archtester gentoo-dev 2012-01-14 22:30:39 UTC
It would probably make more sense to package the P-Touch printer driver for cups.

http://www.diku.dk/hjemmesider/ansatte/panic/P-touch/
Comment 4 Andreas K. Hüttel archtester gentoo-dev 2012-04-08 14:04:37 UTC
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/