Hey,

trying to upgrade gvfs, apt-get wants to install usbmuxd, because of the
following dependency chain:

gvfs → gvfs-backends → libimobiledevice → usbmuxd

it seems that gvfs-backends might include a bit too much backends, but
eventually, I'm wondering why a *lib* depends on a *daemon*.

I definitely don't want to install a daemon to handle a hardware I don't
even have.

Could you reconsider the dependency? If people need to access iStuff,
they can install directly the usbmuxd, but I don't think a lib should
bring it.

Thanks in advance,
--
Yves-Alexis

Hi,

Le jeudi 22 avril 2010 à 21:12 +0200, Yves-Alexis Perez a écrit :
It's needed, because libimobildedevice uses usbmuxd to talk to iStuff
over USB.
Well, without it, AFC backend can't work. Since all gvfs backends are in
1 package, I don't see how it could be avoided.

Regards,
Julien Lavergne

I'm still puzzled about why a *lib* should require a daemon. Maybe the
actual tool/executable should have the dependency, instead?

If you think gvfs-backends should be split, feel free to reassign. But
forcing daemon installation like that makes me feel bad, really.

Cheers,

reassign 578795 gvfs-backends
retitle 578795 split packages for various backends
severity 578795 wishlist
thanks

Ok, reassigning to gvfs-backends. Basically, it'd be nice to split the
backends package in few packages so people can install only the one they
need.

Splitting using one package per backend might clutter a bit too much, so
a proposition could be:

gvfs-backends with only the “standard” ones. Standard is a bit fuzzy,
but basically http/dav/ftp/ssh/cdda/smb/
gvfs-backend-photo with the gphoto2 stuff
gvfs-backend-mobiledevice with the afc/mobiledevice/iphone stuff
gvfs-backend-obex with the bluetooth stack

What do you think?

Just wanted to add some justification for splitting the backends.

I have a non-Apple device (Sansa Fuze; looks like an iPod, has a data port that is
like, but not compatible with, the Apple connector).  It used to be recognized as 1
or 2 USB drives (depending on data card), but with recent distributions it is seen
as a Music Device, accessible only in Rhythmbox.  I uninstalled packages until it
was recognized as a drive again.  Then I couldn't access network shares (Samba).
Researching that problem, I found that re-installing gvfs-backends fixed it, but broke
the Fuze access.

So my best option was to install/uninstall this package depending on what I want to
do.  Looking further, I manually deleted the afs.mount file (only), and everything
works now.

I can image that others may want a choice on how they access devices (although I
don't know if this applies to i-devices, so this may be a rather limited audience).

Hello.
Whether there is a progress in work?
I use XFCE and it is unpleasant to me that gvfs-backends depends on GTK3, Gnome online accounts and other bulky things which I don't use.