dj at linuxfromscratch.org
Thu Sep 24 16:16:39 PDT 2009
On 09/17/2009 08:51 AM, Wayne Blaszczyk wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> DJ Lucas wrote:
> <stuff delete/>
>> Unfortunately, it seems that there are a few bad assumptions in the
>> Gnome autoscripts that didn't used to be there, and these should all be
>> fixed upstream, preferably via pkg-config. I take it that you are not
>> seeing the (suspected) GIO issue mentioned above?
>> -- DJ Lucas
> Sorry, I missed that bit. Yes I have/had the same problem.
> Installing gvfs fixes that problem. I still need to read up on what gvfs
> is and how it differs from gnome-vfs. i.e. is it a replacement or a
> split or a complementary addition. Any input would be greatly appreciated.
> The GDM icon problem has been fixed with the additional step:
> ln -s $(pkg-config --variable=prefix \
> $(pkg-config \
> --variable=prefix ORBit-2.0)/lib/gdm
> GDM assumes that it and gnome-settings-daemon share the same libexecdir.
> How do we raise this problem with the GDM developers?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
Okay...digging into it a bit. Gnome-settings-daemon and ConsoleKit will
both need to provide the libexec dir in their pc files, they currently
do not. So those changes will have to be made and then we can do swap
@LIBEXECDIR@ for @GSD_LIBEXECDIR@ and @CK_LIBEXECDIR@ in the relative
desktop.in files in the gdm sourcetree. It looks like a lot of the
gnome packages should include a libexecdir variable in the pc files, but
currently do not.
-- DJ Lucas
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
More information about the blfs-dev