Douglas R. Reno wrote:
Ken Moffat wrote:
On Thu, Jul 14, 2016 at 10:29:18PM -0500, Douglas R. Reno wrote:
Ken Moffat wrote:
On Thu, Jul 14, 2016 at 09:39:27PM -0500, Douglas R. Reno wrote:
I was going to change the installed libraries section to read (GIO
modules in /usr/lib/gio/modules) at the end.
On reflection, if nothing else creates that directory then I suppose
it should be mentioned in the directories section. But you know
more than I do about which other packages, if any, also install to
that directory.
ĸen
:-) For reference, DConf, Gsettings, Gvfs, and what I believe is
PulseAudio
(? - that is what I am thinking libgio-remote-volume-monitor.so is,
otherwise its GNOME Shell?) install to that directory:
"
$ ls /usr/lib/gio/modules/
giomodule.cache libgioremote-volume-monitor.la
libdconfsettings.so libgioremote-volume-monitor.so
libgiognomeproxy.la libgsettingsgconfbackend.la
libgiognomeproxy.so libgsettingsgconfbackend.so
libgiognutls.la libgvfsdbus.la
libgiognutls.so libgvfsdbus.so
"
Note: that was performed on a fully built and configured GNOME system.
Haven't built GNOME stuff on a Sysv machine yet, so I have no idea how
many
of those apply on those machines. :-)
Looking at my sysv logs from 7.9, /usr/lib/gio/modules was created
by glib2. So maybe we should mention that modules are written there
by other packages. On that build I only had dconf, gvfs, GConf and
glib-networking writing to it.
That seems like a very good solution. Should we put that in each package
page, or just add a note in Glib2?
It will be hard to develop consistency about this for every package where
multiple packages write to a common directory. We ignore /bin, /lib, etc
(pun not intended), but there are several directories in /usr/share and
other places where multiple packages write to common directories.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
