Hi,
Kay requested that we install glib libraries (libglib, libgmodule, libgthread, libgobject and libgio) in /lib instead of /usr/lib as some of the early init action will need glib.
It turns out that glib has a --with-runtime-libdir configure flag that builds glib in /usr/lib but moves the non-devel libraries (*.so.*) to the specific director. This would work fine as glib only links to libraries living in /lib already.
I quickly looked at that and the only downside is that the gio modules and all the gsettings API (from libgio) cannot be used if /usr is not available. I don't expect anything to use those during the early stage of the boot process, so it should be okay.
(Alternatively, we can choose to keep libgio in /usr/lib, but it could well be used, so...)
Any opinion on this?
Vincent
El 12/10/10 09:39, Vincent Untz escribió:
Any opinion on this?
Looks fine to me, while you are at it, --disable-static so we can fix the packages that are using static glib (there are a few ..)
Cheers.
Le mardi 12 octobre 2010, à 10:51 -0300, Cristian Rodríguez a écrit :
El 12/10/10 09:39, Vincent Untz escribió:
Any opinion on this?
Looks fine to me, while you are at it, --disable-static so we can fix the packages that are using static glib (there are a few ..)
I think that last time I looked at this, some people really wanted to use a static glib. rpmlint-mini, for example.
But we could at least move the files to a devel-static subpackage, I guess.
Vincent
El 12/10/10 10:59, Vincent Untz escribió:
I think that last time I looked at this, some people really wanted to use a static glib. rpmlint-mini, for example.
But we could at least move the files to a devel-static subpackage, I guess.
Inlcuding the shared libraries in the package (like it does with libmagic and libpython) is somewhat better for this case.
On Tuesday 12 of October 2010 14:39:39 Vincent Untz wrote:
Hi,
Kay requested that we install glib libraries (libglib, libgmodule, libgthread, libgobject and libgio) in /lib instead of /usr/lib as some of the early init action will need glib.
Isn't that change triggered by systemd? Afaik it uses glib dekstop file parser at least.
Regards Michal Vyskocil
It turns out that glib has a --with-runtime-libdir configure flag that builds glib in /usr/lib but moves the non-devel libraries (*.so.*) to the specific director. This would work fine as glib only links to libraries living in /lib already.
I quickly looked at that and the only downside is that the gio modules and all the gsettings API (from libgio) cannot be used if /usr is not available. I don't expect anything to use those during the early stage of the boot process, so it should be okay.
(Alternatively, we can choose to keep libgio in /usr/lib, but it could well be used, so...)
Any opinion on this?
Vincent
On Thu, 2010-10-21 at 11:04 +0200, Michal Vyskocil wrote:
On Tuesday 12 of October 2010 14:39:39 Vincent Untz wrote:
Hi,
Kay requested that we install glib libraries (libglib, libgmodule, libgthread, libgobject and libgio) in /lib instead of /usr/lib as some of the early init action will need glib.
Isn't that change triggered by systemd? Afaik it uses glib dekstop file parser at least.
Oh no, it does not use glib at all, and probably never will.
And it does not use glib's parse-everything-and-put-all-in-a-hash ini-file parser.
Systemd needs to handle multiple keys with the same name. The systemd ini file parser reads a stream not the entire file.
The glib parser can't even handle some of the systemd config files reliably for that reason.
Kay
On 10/22/2010 03:36 PM, Kay Sievers wrote:
On Thu, 2010-10-21 at 11:04 +0200, Michal Vyskocil wrote:
On Tuesday 12 of October 2010 14:39:39 Vincent Untz wrote:
Hi,
Kay requested that we install glib libraries (libglib, libgmodule, libgthread, libgobject and libgio) in /lib instead of /usr/lib as some of the early init action will need glib.
Isn't that change triggered by systemd? Afaik it uses glib dekstop file parser at least.
Oh no, it does not use glib at all, and probably never will.
Urhm, doesn't it use dbus-glib-1 ? At least that's what I can see in http://cgit.freedesktop.org/systemd/tree/configure.ac
On Mon, 2010-10-25 at 14:58 +0200, Pavol Rusnak wrote:
On 10/22/2010 03:36 PM, Kay Sievers wrote:
On Thu, 2010-10-21 at 11:04 +0200, Michal Vyskocil wrote:
On Tuesday 12 of October 2010 14:39:39 Vincent Untz wrote:
Hi,
Kay requested that we install glib libraries (libglib, libgmodule, libgthread, libgobject and libgio) in /lib instead of /usr/lib as some of the early init action will need glib.
Isn't that change triggered by systemd? Afaik it uses glib dekstop file parser at least.
Oh no, it does not use glib at all, and probably never will.
Urhm, doesn't it use dbus-glib-1 ? At least that's what I can see in http://cgit.freedesktop.org/systemd/tree/configure.ac
That's only a pretty dumb gtk tool, a D-Bus based frontend to systemd, that can manage services. It's optional, and it's in its own package, and not very useful at the moment.
Kay
On 10/25/2010 03:15 PM, Kay Sievers wrote:
On Mon, 2010-10-25 at 14:58 +0200, Pavol Rusnak wrote:
On 10/22/2010 03:36 PM, Kay Sievers wrote:
On Thu, 2010-10-21 at 11:04 +0200, Michal Vyskocil wrote:
On Tuesday 12 of October 2010 14:39:39 Vincent Untz wrote:
Hi,
Kay requested that we install glib libraries (libglib, libgmodule, libgthread, libgobject and libgio) in /lib instead of /usr/lib as some of the early init action will need glib.
Isn't that change triggered by systemd? Afaik it uses glib dekstop file parser at least.
Oh no, it does not use glib at all, and probably never will.
Urhm, doesn't it use dbus-glib-1 ? At least that's what I can see in http://cgit.freedesktop.org/systemd/tree/configure.ac
That's only a pretty dumb gtk tool, a D-Bus based frontend to systemd, that can manage services. It's optional, and it's in its own package, and not very useful at the moment.
Ah, thank you for clarification!
Kay
-
Cristian Rodríguez -
Kay Sievers -
Michal Vyskocil -
Pavol Rusnak -
Vincent Untz