[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-packaging
Subject:    Re: [opensuse-packaging] question on packaging and gconf failures
From:       Rauch Christian <info () rauch-webdesign ! de>
Date:       2006-10-09 16:46:10
Message-ID: 452A7CD2.3020809 () rauch-webdesign ! de
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stanislav Brabec schrieb:
> Or better configure with --disable-schemas-install
> 
>> According to http://www.gnome.org/projects/gconf/ (Section Application
>> developer information), this is known and they tell a workaround there.
>>
>> Is this the established way to workaround this or is there a "suse way"
>> to do this?
> 
> Yes:
> 
> 1)
> Never install gconf database to build root. Use
> --disable-schemas-install or GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1.
> 
> 2) Use %post
> 
> %post
> export GCONF_CONFIG_SOURCE=`opt/gnome/bin/gconftool-2 --get-default-source`
> opt/gnome/bin/gconftool-2 --makefile-install-rule etc/opt/gnome/gconf/schemas/foo.schemas >/dev/null
> (one line per each schemas file)
> 
> 3) Don't use %postun. RPM cannot do it correctly:
> http://bugzilla.gnome.org/show_bug.cgi?id=306924
> 
> 4) In file list, never use *.schemas
> /etc/opt/gnome/gconf/schemas/foo.schemas
> (one line per each schemas file)
> It is cosmetic, but prevents upgrading with missing lines in %post.
> 

Thanks a lot for this instructions, y2pmbuild is currently running and
building i686 and x84_64 for 10.0, 10.1 is already finished!

Regards,
Rauch Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFFKnzSayhvFxrDZlkRAgH3AJ9hSQD7pDfhi8/JJ0Bgoyokx04PJACdF7Se
q1qRj/7zbFVmBPOITBHruKo=
=p5PS
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-packaging+help@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]