Le lundi 30 juin 2008 à 12:53 +0100, Neil Williams a écrit : > It works (so far) but lintian gives a warning: > W: estron-gnome: gconftool-used-in-maintainer-script postinst:45 > N: > N: This script apparently runs gconftool or gconftool-2. It should > N: probably be calling gconf-schemas or update-gconf-defaults instead.
> Well, the postinst does call gconf-schemas via dh_gconf to put the gconf > schemas into place, but the 'defaults' aren't known before dbconfig is > run so I can't put the defaults into the package itself. Hence the > postinst calls dbconfig, then all the debhelper routines and finally, > inserts the dbconfig data into the gconf structure created a moment > before by debhelper, by calling gconftool-2 with the data from dbconfig. This is an interesting use. The GConf Debian packaging was not directly meant for such things, but it is easy to use it this way. Just ship a /usr/share/gconf/defaults/10_estron-gnome symbolic link to somewhere in /etc. In the postinst, generate the file in /etc before #DEBHELPER# and you should be fine (dh_gconf should add a call to update-gconf-defaults). You should not call gconftool directly, since it modifies the system-wide defaults, in which you have no easy way to tell whether the sysadmin has already modified the values. This is why gconftool should remain the sysadmin’s tool and not used by packagers. I don’t think it is wrong to use GConf for such things; just the opposite, as GConf was precisely designed for layered configuration. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
