Summary: | ebuild for pyusb-0.3.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Torsten Kurbad <torsten> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | denilsonsa, josejx, rbu |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://pyusb.berlios.de | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
pyusb-0.3.5.ebuild
pyusb-0.3.5.ebuild pyusb-0.3.5-name.patch |
Description
Torsten Kurbad
2007-04-27 21:23:12 UTC
Created attachment 117446 [details]
pyusb-0.3.5.ebuild
Created attachment 117453 [details]
pyusb-0.3.5.ebuild
New version of the ebuild that honors a local use flag "vfd". This triggers the patch (s. next attachment) to get freevo's vdf-plugin running.
Created attachment 117455 [details, diff]
pyusb-0.3.5-name.patch
Put into files dir.
Support for the VFD on the Shuttle M1000 is available for lcdproc as a patch and might be part of the next lcdproc release. This way, you could add support for that VFD on the pylcd -> lcdproc way, too. Would there be any advantages with the vfd-plugin -> pyusb way? Hmm, don't know really - I think, freevo would be capable to deal with lcdproc, too. Thus, there's no real need. Anyway, this is a generic module to access to USB bus, it wasn't specifially designed for the VFD, so maybe it won't hurt putting it in portage... ;o) Regards, Torsten In case the lcdproc patch gets accepted, I'd recommend you to test that. Otherwise, I don't see much sense in maintaing it unless someone uses it. And once it's needed, the ebuild is here in bugzi (which is nice). Sounds like a plan to me... ;o) have a look at bug #135373 ... I long since have my own customized 0.4.0 ebuild in the overlay... ;o) Regards, Torsten *pyusb-0.4.1 (28 May 2009) 28 May 2009; Joseph Jezak <josejx@gentoo.org> +metadata.xml, +pyusb-0.4.1.ebuild: Initial commit. |