Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 370483 - ebuild request brother mfc-j265w lpr & cupswrapper ebuilds
Summary: ebuild request brother mfc-j265w lpr & cupswrapper ebuilds
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Default Assignee for New Packages
Depends on: 399875
Blocks: printer-drivers
  Show dependency tree
Reported: 2011-06-07 16:45 UTC by Andreas Mielke
Modified: 2017-02-19 17:57 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Ebuild vor Brother MFC-J265w (brother-mfc-j265w-drivers-1.ebuild,1.92 KB, text/plain)
2011-07-13 13:17 UTC, Andreas Mielke

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Mielke 2011-06-07 16:45:34 UTC
ebuilds to merge brother drivers for Brother MFC-J265W

Reproducible: Always
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2011-06-09 22:26:32 UTC
Is this some kind of request?
Comment 2 Andreas Mielke 2011-06-10 05:43:35 UTC

I did not want to be rude.

Ebuild request for brother driver MFC-J265W.

For more information see here:
Comment 3 Andreas Mielke 2011-07-13 13:17:00 UTC
Created attachment 279989 [details]
Ebuild vor Brother MFC-J265w
Comment 4 Andreas K. Hüttel archtester gentoo-dev 2012-04-08 14:01:44 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 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]), 
* ...

Comment 5 Andreas K. Hüttel archtester gentoo-dev 2017-01-28 22:54:03 UTC
Is anyone still interested in this?
Comment 6 Andreas K. Hüttel archtester gentoo-dev 2017-02-19 17:57:52 UTC
(In reply to Andreas K. Hüttel from comment #5)
> Is anyone still interested in this?

Seems not