On 02/07/2010 06:56 AM, Alonso Graterol wrote: > >> 0228-gnome-screensaver-2.28.1 >> 0229-gnome-volume-manager-2.24.1 >> 0230-gnome-utils-2.28.3 >> 0231-gvfs-1.4.3 (yes, it was installed multiple times while fixing the gio >> modules, patch needed for alternate prefix) >> 0232-gvfs-1.4.3 >> 0233-yelp-2.28.1 >> >> >> > > Lucas, > > Yesterday I could learn that glib uses a configuration parameter for > instructing gio of alternate directories where to look for modules to > load so with your installation planned you can tell glib beforehand > where to look. > > In my case glib-2.22.4 was configured with --with-prefix=/usr > --with-pcre=system --with-gio-module-dir=/opt/gnome/lib/gio/modules > (this is where gvfs installed its modules). First time I built glib I > did not use it and ended with Nautilus unable to handle computer:///, > network:/// and the like. > Thanks for that bit of info. Yes, those solutions should work as well, however, the point of separating Gnome packages is that Gnome stuff goes into the alternate directory and can be removed/upgraded easily (by changing a symlink). It would be nice if GIO could be configured at runtime with a search path. The best solution I came up with was to patch gvfs, so that if the /opt/gnome directory is removed, you haven't broken GIO, only some invalid items in /usr/lib/gio/modules that would be overwritten on a new installation of Gnome. There used to be a search path environment variable that could be set "GIO_MODULE_DIR", but as of Gnome-2.26.x it no longer worked, and was to be a single directory, not a colon separated search path. I admit I hadn't tried it, or even looked for it on this build as I forgot about it until you mentioned it, but still the same.
-- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
