Re: new dependencies in gvfs

[Matthias Clasen <matthias clasen gmail com>]

2009/5/30 BJörn Lindqvist <bjourne gmail com>:
> Many of those
> packages are not packaged in Ubuntu Intrepid and at least and some of
> them haven't had any real releases yet.

It builds fine in Fedora 11...


> There are at least two build bugs related to gdu (583704, 582096).

I'll see if I can get those fixed.


> In short, IMHO it is premature to include gdu in jhbuild because the
> project is not batch buildable which is the point of jhbuild.
>
> I also hope that there will more documentation available about gdu
> before it becomes a blessed external dependency because there is very
> little of that available atm, especially why HAL is being replaced and
> what advantages that brings.

Here are some relevant posts
http://lists.freedesktop.org/archives/hal/2008-May/011560.html
http://lists.freedesktop.org/archives/devkit-devel/2009-April/000140.html
http://blog.fubar.dk/?p=105


> Also shouldn't the gui parts be split from the backend? The repository
> seem to mix both the backend library with frontend tools.

The 'backend' is DeviceKit-disks, which is separate already.
gnome-disk-utility contains a collection of GUI pieces
(nautilus-extension, formatting tool, standalone disk utility, etc).
In addition, there is a gobject-based library that contains code that
is shared by all the utilities (that is also what the gvfs backend
uses out of gnome-disk-utility).

I don't think it makes much sense to split this library out at the
source level; distros might of course decide to ship it as a separate
gnome-disk-utility-libs package (as we do in Fedora).


Matthias