On 02.02.2011 23:29, Martin Langhoff wrote:
thoughts?
I think udev rules should be in the package driving the hardware, not
somewhere else in a robot-control package. For example,
openni-primesense (in review) carries such a file for the PrimeSense and
Kinect, and I don't see that this should belong anywhere else. I don't
like that centralization.
I also agree with Tim. If there are any kind of drivers or libraries
which is used for accessing a specific hardware, corresponding udev
rules can be packaged with that driver of library.
I'd think different if I'm just misunderstanding your proposal and you
are in fact proposing some kind of framework. So your package would
setup a group to which robot devices can be assigned, which are then
magically accessible by the console user, and for which hardware
packages only contain udev rules of the form "device identifier ->
assign to robot group". But then, why not add this framework to the udev
package in the first place?
Tim