Bug#382195: Offer of Assistance
On Thursday 01 February 2007 03:57:26 am you wrote:
> Indeed, adding a mtp-tools package was straightforward. See [1].
Great. Package installed fine and works perfectly.
Not sure what to do about the man pages. These tools are all very tiny and
not exactly used for much other than testing your libmtp install. What if
one man page were written with just a very general explenation of how to use
the tools and then use that as the man page for all of them? I feel like
this is done with other packages that have a bunch of tiny binaries.
> I also fixed a problem with the udev rules file. The most recent
> debian/changelog entry reads:
>
> libmtp (0.1.3-0.2) unstable; urgency=low
>
> * Non-maintainer upload
> * Created package mtp-tools containing the programs distributed in the
> examples directory
> * debian/control: Added my name to Uploaders
> * debian/rules:
> - Clean files libmtp.rules, libmtp.fdi, and libmtp.usermap generated
> at build time, such that they do not appear in the diff.gz
> - Instead of installing debian/libmtp.rules, change the libmtp.rules
> generated at build time to follow the Debian standards (MODE="660",
> GROUP="audio")
Is audio the right group? I've alwasy been confused by how udev OUGHT to
work, so I'll defer to experts, but it seems to me that having access to the
audio device on the system is different than having the ability to write to a
usb device. I set mine to plugdev, only because it seems to have to do with
people who 'plug' things in. But, like I said, I have no idea how this is
supposed to work. Perhaps the policy says something?
-Sean
--
Sean Kellogg
e: skellogg@gmail.com
w: http://blog.probonogeek.org/
So, let go
...Jump in
...Oh well, what you waiting for?
...it's all right
...'Cause there's beauty in the breakdown
Reply to: