Mailinglist Archive: opensuse-bugs (15077 mails)
| < Previous | Next > |
[Bug 245550] gconftool-rebuild handling during system upgrade illogical
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 11 Sep 2007 11:45:49 -0600 (MDT)
- Message-id: <20070911174549.97ECF245350@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=245550#c4
Stanislav Brabec <sbrabec@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #4 from Stanislav Brabec <sbrabec@xxxxxxxxxx> 2007-09-11 11:45:49 MST ---
> Do not move etc/opt/gnome/gconf/gconf.xml.schemas to
etc/gconf/gconf.xml.schemas. Instead, include compatibility etc/opt/gnome
search paths in /etc/gconf/2/path.
But standard old-style scriptlets install to the default location. On upgrade
of any /opt/gnome package, we'll have two set of keys.
> Do not call gconftool-rebuild.
The best solution for future, but after upgrade protection from SLED10 expires
(to never keep orphans).
> Re-add /etc/opt/gnome/gconf/schemas to the directories processed by
gconftool-rebuild.
Yes, it seems to be acceptable.
> Another theoretical option is moving even the .schemas files from
/etc/opt/gnome/gconf/schemas to /etc/gconf/schemas, but this contradicts
packaging principles (situation on disk should be == situation in rpmdb).
No chance. It will either break fs<->rpmdb consistency (no symlink), or rpm
will break it totally (symlink to /etc will confuse rpm)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Stanislav Brabec <sbrabec@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #4 from Stanislav Brabec <sbrabec@xxxxxxxxxx> 2007-09-11 11:45:49 MST ---
> Do not move etc/opt/gnome/gconf/gconf.xml.schemas to
etc/gconf/gconf.xml.schemas. Instead, include compatibility etc/opt/gnome
search paths in /etc/gconf/2/path.
But standard old-style scriptlets install to the default location. On upgrade
of any /opt/gnome package, we'll have two set of keys.
> Do not call gconftool-rebuild.
The best solution for future, but after upgrade protection from SLED10 expires
(to never keep orphans).
> Re-add /etc/opt/gnome/gconf/schemas to the directories processed by
gconftool-rebuild.
Yes, it seems to be acceptable.
> Another theoretical option is moving even the .schemas files from
/etc/opt/gnome/gconf/schemas to /etc/gconf/schemas, but this contradicts
packaging principles (situation on disk should be == situation in rpmdb).
No chance. It will either break fs<->rpmdb consistency (no symlink), or rpm
will break it totally (symlink to /etc will confuse rpm)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |