It was interesting to test and implement in order to find out how extended attributes work. Not everything implemented has to be something that would actually become something users would use or even usable in the general sense.

Please tell me this is an elaborate hoax.

Awesome! I'm so glad that you implemented and tested this, since it's the same as an idea I had a while back.

Profiling sounds like a great idea. Might be that the performance would out-do current if a bug or few get fixed.

How's the cold-cache comparison? I'd expect that accessing half the number of files (ebuild only instead of cache+ebuild) doesn't improve performance.

+1*10^6 :)

Seems that proper command is:
layman -a java-overlay

instead of simply "java"

Thanks :-)

It seems there's a new version of the MX-5500 mouse with the same vendor and product ID, but that communicates differently, and revoco hasn't been updated to work with it. It detects the MX-5500 and prints the warning about it being experimental, but ultimately doesn't work

At work, I have the previous version and it works great to change mode. But at home, I have the newer one, and it doesn't work. Unfortunately I'm not familiar enough with libusb to see immediately why it's failing. I do have several notes from a usbmon dump while using VirtualBox/XP to control the mouse, and have identified several features of both the keyboard and the mouse, in case anyone would like to take a stab at fixing revoco's support or writing an additional application for working with the keyboard. Feel free to contact me for the usbmon dump and notes.

The ebuild-link does not work. :(

I am not sure what you mean by "parse the bugzilla open bugs", but wouldn't it be possible to to a query against the bugzilla db for zero hits, and only then add them to the feed? I have been following the feed for a bit now and there seems to be quite alot of them.

RSS::Maker in ruby standard library but the RSS 2.0 standard is so simple that it's not that hard with any good generic xml library either.

I'm curious what you used to generate the rss feed. Not the necessary portage-fu (to get the ebuilds, etc) but actually how the rss was generated.

I went looking for an easy to use rss generator a few months ago and came up with nothing.

Anyway, I'm just curious :)

I am completely new to Ubuntu 8.10

I got so far as to download and extract. I went to the directory I extracted it in, and typed "make". Now I have 2 new files: revoco, and revoco.o

What do I do next to get this working. Please help.

@HS: yea, until then..
@tiago: Please reread the post. 30 days in tree, no bugs.
@bbroeksema: Possibly. One such way would be to use pcheck from pkgcore-checks. cd into the directory you want to check, run pcheck. Then look for:
dev-php/PEAR-Log
StaleUnstableKeyword: version 1.9.13: no change in 318 days for unstable keywords [ ~alpha, ~amd64, ~arm, ~hppa, ~ia64, ~ppc, ~ppc64, ~s390, ~sh, ~sparc, ~x86 ]

(for example)

Granted, you will have to check for false hits, etc

HTH.

Thank you for that! I was looking for an easy way to help my favourite distro. I have just filed my first stable request bug.

Well this is a useful post and the first time since using Gentoo (~6 years now) I feel like helping out a bit. Do you know a handy trick (e.g. some shell script or so) to determine how long an ebuild is in the tree?

i'd love to, but, what are the requirements for an ebuild to be stable?

Yeah, good idea. However I think it _should_ exist some automatically generated list of such ebuilds (no bugs, at least one month in testing). Possibility that developer can subscribe for announcements would be also good benefit).

Hi, I just got a MX Revolution as well. revoco worked a couple of times, but now it will not actually change the mode of the wheel. I can set free spinning mode, and revoco will report that's the mode if I query it, but the wheel is constantly in ratcheting mode. Has anyone else had revoco appear to be working on the software side but not actually do anything to the mouse?

PS This blog does not let me post a comment with my gmail address, thanks!

Hi,
I just bought a MX 5500 Logitech kit, it has a MX Revolution mouse connected with bluetooth, but revoco doesn't seem to work for me, i run it as root, it returns no error but the mouse behaviour does not change, i run revoco manual=6 or manual=13 but the middle button still is the one in control over the scroll mode.
Any sugestions/tips would be appreciated :)

For those who want to use wheel-click to toggle between free and click-for-click, you can use xmodmap to remap your middle click to another button. I use this in my ~/.Xmodmap:

pointer = 1 9 3 4 5 7 6 8 2 10 11 12 13 14 15 16 17 18 19 20

This makes the "forward" thumb button a middle mouse button. I find this much easier to press than the wheel itself!

Hi, and thanks for that fantastic info! This should be on the gentoo-wiki...

A few tips for using my MX Revolution:

1. I had to edit revoco-0.3.c and change:
#define MX_REVOLUTION to 0xc525 as my usb id is slightly different. (DrDrew: your problem? use `lsusb`)

2. The auto setting was a bit spastic by default - the solenoid was clicking on and off without even moving. This worked:
$ sudo revoco auto=10
(Froese - could this be your problem?)

3. setting the manual click change to button "6" (find button) gives me my middle click back *woot*
$ sudo revoco manual=6
and also gets rid of that annoying "search" keyevent which I have a keyboard for :)

4. ... But unfortunately, when I set the manual=6 option, the auto scroll feature turns off again :|

But that's a small price to pay! Thanks for finding and documenting this! Now I can show off to my friends :)