I'm not a big fan of having gnome-vfs seeming to depend on gtk+. This will lead people to believe that gtk+ is a required dependency for gnome-vfs and that they can't use it without gtk+ and all its dependencies. There is already confusion about that (probably caused by the gtk dialog which comes with gconf), see http://mail.gnome.org/archives/gnome-vfs-list/2003-October/msg00007.html This shows once again (the problem already appeared with the gnome-vfs authentication dialog which was added in libgnomeui) that we need some kind of libgnomeui library which can act as a glue between gconf, gnome-vfs and gtk+ Christophe > Who gives a crap if you have to build gtk+ before gnome-vfs? In fact > "jhbuild list" shows that gtk+ already builds before gnome-vfs. > > The foo/fooui library splits were done to allow apps to avoid relying on > an X connection, or linking to all the X/GTK+ libs if they aren't GUI > apps. But what we're talking about here has nothing to do with that. > It's simply an issue of the build graph. And there are no requirements > on the build graph other than "no cycles" > > Havoc > > > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list gnome org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e=2E?=