Tracker for drivers which will be removed in the near future. The other tracker (bug #276822) should be for drivers that we don't (yet) intend to treeclean but are in desperate need of love.
Ok, so all the drivers here are the ones that : 1) are currently broken, 2) are marked as unmaintained by upstream. I think all of these should be removed from INPUT_DEVICES in all versions of xorg-server (-9999 in the overlay is already fixed) and then p.masked from portage. Donnie and @herd, what say you? I'd like to get rid of these really soon (ie, by the end of the week) since they're just cruft polluting portage. Thanks
Ack, we should probably keep only synaptics keyboard mouse and evdev. (and what ever upstream say is supported)
(In reply to comment #2) > Ack, we should probably keep only synaptics keyboard mouse and evdev. (and what > ever upstream say is supported) > What does one use in place of x11-drivers/xf86-input-spaceorb ? The Engineering dept where I work retired their old serial ones and I took one home to hook up to my machine to see what I can do with it. It's a IBM SpaceBall 4000FLX ("Manufactured for IBM by 3Dconnexion" it says on the bottom) M.
(In reply to comment #3) > (In reply to comment #2) > > Ack, we should probably keep only synaptics keyboard mouse and evdev. (and what > > ever upstream say is supported) > > > > What does one use in place of x11-drivers/xf86-input-spaceorb ? The > Engineering dept where I work retired their old serial ones and I took one home > to hook up to my machine to see what I can do with it. It's a IBM SpaceBall > 4000FLX ("Manufactured for IBM by 3Dconnexion" it says on the bottom) > > M. > I'm sorry to reply to myself, but, according to the bug #276619: "This bug is fixed in X.org git repository" Am I to assume that it's still supported by X.org? Why would it still be removed from portage if it's a supported driver? I'm more just curious at this point than I am arguing for trying to keep it. I haven't yet tried to install it and see what I can do with the (older...) SpaceBall I have now.
(In reply to comment #4) > I'm sorry to reply to myself, but, according to the bug #276619: > > "This bug is fixed in X.org git repository" The build issue might be fixed, but the latest commit is very clear : http://cgit.freedesktop.org/xorg/driver/xf86-input-spaceorb/log/ > I'm more just curious at this point than I am arguing for trying to keep it. I > haven't yet tried to install it and see what I can do with the (older...) > SpaceBall I have now. Honestly, I have no idea what this device is and what its support is supposed to be. Maybe there's a Linux kernel driver for it, which would be much better than an X driver. As for support within portage, that probably won't happen, we already have too many ebuilds to take care of. But we can probably work something out in the x11 overlay. But first, you should get in touch with upstream X developers to see what kind of work is required to get it working. I don't mind helping out, but this driver (almost definitely) will not go back to portage... unless maybe you find a dozen other Gentoo users with this hardware :) If you have further comments, let's talk directly on the specific spaceorb bug instead of here, this is a tracker. Thanks
(In reply to comment #2) > Ack, we should probably keep only synaptics keyboard mouse and evdev. I second that; I have not really understood the rationale for removing synaptics. As far as I can tell, it's a driver for Synaptics touchpads; my 4-year-old Fujitsu-Siemens Amilo Pro uses it, and it has worked fine ever since (and I understand the technology is used in many laptops!). The mere fact that it's no longer being maintained upstream does not convince me that it should be removed (perhaps it does not need maintaining because it just works?). After all, that would leave me with an unusable touchpad. Can you elaborate, please? Or, if there are compelling reasons to drop it, is there a replacement?
(In reply to comment #6) > (In reply to comment #2) > > Ack, we should probably keep only synaptics keyboard mouse and evdev. > > I second that; I have not really understood the rationale for removing > synaptics. I dropped x11-drivers/synaptics, I did *not* drop x11-drivers/xf86-input-synaptics...
adding citron and elographics, they actually were not even part of xorg 7.4...
Closing this tracker, we can use the remaining tracker (bug #276822) from now on. Thanks
