Le vendredi 13 octobre 2006 à 13:53 -0700, Steve Langasek a écrit : > Hi Josselin, > > On Wed, Oct 11, 2006 at 09:56:20AM +0200, Josselin Mouette wrote: > > > The /etc/gconf/schemas/ggz-gnome.schemas file contains GConf schemas > > which have nothing to do in /etc. They have to be moved to /usr/share to > > comply with the Filesystem Hierarchy Standard. > > Could you comment whether having them in /etc breaks anything > functionality-wise? The line between configuration data and > non-configuration data is a blurry one in the FHS, and often doesn't warrant > a release-critical bug.
Schemas are not meant to be configurable. The place for setting default values for the administrator is /etc/gconf/gconf.xml.defaults. If someone changes the schemas, they have to be registered again - in a way that is not well documented - otherwise the change won't be taken into account, and default values that don't correspond with the schema anymore won't be removed at the time of schema un-registration. Which means cruft can be let in /etc/gconf/gconf.xml.defaults at the time of package purge. Furthermore, this package didn't even register the schemas as defaults, which means the default values weren't even available to the application. Depending on the application, it can generate a warning or simply not work at all. Maybe I should find some time to write up a small policy document based on what dh_gconf does and why. Currently, all packages using GConf build with debhelper one way or another and I have ensured they all use dh_gconf. -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
signature.asc
Description: Ceci est une partie de message numériquement signée
