- esound (raise the bugs to Serious?) [1]
- gconf-editor (no rdeps, we really want to discourage gconf use)
On Fri, 22 Dec 2017 at 22:57:43 -0500, Jeremy Bicha wrote:
- esound (raise the bugs to Serious?) [1]
If we want to remove that, raising the bug severities would be a prerequisite. (We should certainly either remove it or orphan it.)
- gconf-editor (no rdeps, we really want to discourage gconf use)
On one hand, we want to kill off gconf altogether; on the other hand,
as long as gconf hasn't been fully removed, perhaps it makes sense to
have its editor too?
That makes sense, as long as the list of gconf-using packages in
Testing is so long, it doesn't really help us much to drop
gconf-editor early.
Is there a guide for moving from GTK+ 2 and gconf to GTK+ 3 and GSettings?
Is there a guide for moving from GTK+ 2 and gconf to GTK+ 3 and GSettings?
Is there a recommended method for migrating user settings to GSettings?
To be clear, we aren't dropping gtk2 from Buster.
Sure, try this:
https://developer.gnome.org/gio/stable/ch34.html
for gtk2 → gtk3, see
https://developer.gnome.org/gtk3/stable/migrating.html
and can I assume you saw this notice? https://lists.debian.org/debian-devel/2017/10/msg00299.html
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 05:23:15 |
Calls: | 7,467 |
Calls today: | 3 |
Files: | 12,691 |
Messages: | 5,628,213 |