Bugzilla Bug 80623

Hi!

I have created an ebuild for the drivers for the nostromo n50 speedpad. Some infos can be found here: http://catalog.belkin.com/IWCatProductPage.process?Merchant_Id=&Section_Id=2071&pcount=&Product_Id=107727

There are drivers that work with linux, so I created an ebuild. To use the n50, you need to have Event interface support enabled in the kernel, the ebuild will check for that. It's not as nicely written as it should, because I don't know too much about eclasses, but it does its job.

After the driver has been installed, all you need to do is start nostromo_daemon and use nostromo_config to setup your key bindings.

The homepage of the driver project on freshmeat: http://sourceforge.net/projects/nostromodriver/

Suggestions, comments and even complaints are welcome ;)

Thomas

Created an attachment (id=50276) [edit]
nostromo_n50-1.1b.ebuild (Gamepad driver)

either of you want this?

Not a kernel driver.

Created an attachment (id=75714) [edit]
Ebuild for nostromodriver 1.2

This is an updated ebuild for 1.2, which adds support for the N52. I've also
altered the method of checking whether INPUT_EVDEV support is in the kernel to
one which also works for built-in support.

Forgot to mention: Also note that nostromodriver no longer depends upon scew.

Created an attachment (id=75750) [edit]
Ebuild for nostromo_n50 1.2

Updated the dependencies

Created an attachment (id=75751) [edit]
Ebuild for nostromo_n50 1.2

Updated dependencies again

Created an attachment (id=76307) [edit]
1.3 ebuild update

This seems to work.

I put it under x11-misc in my /usr/local/portage/ overlay.  That seemed the
best location for it.

This has to be compiled under X by a user that has access to the running X
process.  In my case I was logged in to X as my user, and su'd to root in an
xterm.  I had to issue 'xhost +' in order for it to compile.  I am not sure why
this is.

Why does it check the location of the kernel?  It is not building modules so
this seems to be a waste.

Scott  =)

Created an attachment (id=89414) [edit]
nostromo_n50 1.3 modualr x compatible ebuild

Updated ebuild that should be modular X compatible.

JESUS CHRIST WHEN IS THIS GOING TO BE INCLUDED IN PORTAGE ALREADY? I've been
using the nostromo driver for over a year and this has been going on forever,
just finish the damn thing already!

P.S. Thanks Allen Brooker for improving the ebuild.

http://www.gentoo.org/proj/en/desktop/games/#doc_chap5_sect10

Are you aware that clicking/posting that link does not actually insert that
ebuild into portage?

Look, I've been patient. But over a year of waiting is ENOUGH!

Why don't we all just stop maintaining the tree then and simply check all
ebuilds on bugzilla and build the entire trees ourselves in overlay
directories, what a wondering distribution that would be!

I meant to say *what a wonderful distribution that would be. Don't blame me I'm
just putting in as much effort typing here as the developers put into adding
new ebuilds.

Alex: Please stop posting. You are doing nothing to increase the chances of
this package making it into portage. The fact is that the Nostromo isn't that
widely a used peice of hardware as far as I'm aware, the package isn't very
frequently maintained upstream and the Games team (amoung the many other
developers) have hundreds of bugs open for packages that already exist in
portage and far more people use than would use this package.

If you want to use the package, download it and put it into your local overlay
- that's the primary reason I put it in bugzilla. I personally wouldn't be
surprised if this package never makes it into portage, but people search for
these things on Bugzilla.

If you really want to get this package into portage, become a developer and
help the games team fix all their existing bugs so they have the time to work
on this one.

If you'd bothered to read the link posted this information would have been
plain to you.

Now please, I beg you, stop posting on this bug - you're doing nothing but
annoying the developers and getting yourself a reputation - a bad one!

This is not the way to treat developers!

So if the developers are so busy, buy how do they find the time to include some
obscure console stock ticker that is so unpopular that nobody except me even
filed a bug that it was discontinued for over a year? Please show me some more
bugs that have been in bugzilla for a year and a half.

How is it that over 1 and a half years not a single damn developer was able to
include this ebuild?

I did read that link and that's what pisses me off. I should be able to ask
after one fucking year!

And I do use this an overlay, but that's not an excuse to have this ebuild
neglected.

And as far as posting, I don't really give a shit any more. This is what always
happens, I run out of tolerance for some shit in gentoo and then I go extreme
which ends up getting me banned.

Bunch of fucking leftist liberal commie anti-white pussies. 

SCHNELL SCHNELL :=)

How will they ever find the the time to include ebuilds when they're all busy
arguing for gay marriage and getting fucked up the ass by Curtis?

     ___
|   |      W H I T E
|___|___   P R I D E
    |   |  W O R L D
____|   |  W I D E !

Bunch of faggot liberal hippies, get off your bongs AND GITR DONE!

/me waits for emails from communist admins

Restricting bug due to abuse...

If anyone is wondering how to contribute to this bug in a more serious fashion,
one suggestion would to be to offer this hardware to a developer under the
adopt-a-developer project. See
http://www.gentoo.org/proj/en/userrel/adopt-a-dev/