The section of the packaging guidelines covering gconf can probably be removed since GNOME has not used gconf for more than 12 years now.
Aren't there still applications that use GConf2? I suppose we'll need to keep the guidelines until they are gone or ported to dconf :/
Still 16 packages that use the Gconf scriptlets:
alexandria.spec gconf-editor.spec gnome-do.spec gnome-translate.spec gnome-vfs2.spec gphotoframe.spec ignuit.spec icedtea-web.spec libgnome.spec mail-notification.spec teg.spec tomboy.spec ucview.spec ufraw.spec byzanz.spec cdcollect.spec
So maybe a better question would be whether anything is supposed to be using it currently, and if not then how to get them fixed to not use it.
Everything using gconf should migrate to gsettings or something else. That said, applications still using gconf are probably very old and unmaintained, so I wouldn't expect it.
One possibility is that someone could look into implementing file triggers on the schema directory that would just do all of this stuff automatically (assuming that didn't somehow happen already) and then just remove the scriptlets from those few packages that still use them. And then of course the guidelines could go away. But I guess at this point it's a question of whether it's worth the effort.
Also note that at least alexandria has an active upstream and so is definitely maintained. Not that I know anything about it, of course. I would assume there is some reason it still uses gconf.
So I guess I'll close this, but do let us know if somehow packages stop using those scriptlets and we'll happily remove them from the guidelines.
Metadata Update from @tibbs: - Issue close_status updated to: rejected - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.