On 09.03.2011 19:08, Martin Langhoff wrote:
On Wed, Mar 9, 2011 at 1:04 PM, Tim Niemueller
<tim(a)niemueller.de> wrote:
> As I suggested earlier, I'm strict against a catch-all robots-udevrules
Happy to rename it to something narrower. Can you look at this list
http://wiki.laptop.org/go/11.2.0/Robotics_plan#Test_matrix and help me
figure out how we can refine the name? These robots and boards have a
few things in common:
- they are usb (some bluetooth)
- they have an education focus
edurobots-udevrules?
That still is way to vague. I suggest creating a package per
robot/board/platform/sensor/actuator. If there is a canonical software
package for a particular robot, e.g. a library most commonly used to
access it, pack the rules in there (examples are libphidget or
libunicap). Arduinos are not even robot-specific, so it would be even
more terrible to stuff that into this package. There seems to be an
arduino package. Having a noarch arduino-udevrules sub-package seems to
be the most sensible, or at least a separate package of that name.
Please do not try to pocket all kinds of hardware into a single package
just because that's they way you use it in your context.
Tim
--
Tim Niemueller <tim(a)niemueller.de>
www.niemueller.de
=================================================================
Imagination is more important than knowledge. (Albert Einstein)