Hallo.
I want to discuss a design problem of GConf --makefile-uninstall-rule.
I have been searching for the reason, why GConf database contains
obsolete keys after correct package update. I found that it is a
concept problem, which affects many packaging systems:
GConf expects following update
gnome-media was branched for 2.12 (I think Ronald did this recently but
it looks like no mail was sent out to announce it).
All bug fixes for 2.12 releases should go on the gnome-2-12 branch.
HEAD will now start merging patches for UI changes and GStreamer 0.10
integration.
Thomas
Dave/Dina :
Frustrated by my inability to easily find a string freeze explanation, I
created http://live.gnome.org/MaintainersCorner_2fStringFreeze based on
a mail from Christian Rose during the 2.9 cycle. Feel free to further
change the page or suggest places in the wiki to link from to this page.
Thomas
On 1/10/06, Thomas Vander Stichele [EMAIL PROTECTED] wrote:
Frustrated by my inability to easily find a string freeze explanation, I
created http://live.gnome.org/MaintainersCorner_2fStringFreeze based on
a mail from Christian Rose during the 2.9 cycle. Feel free to further
change the page or
On Tue, 2006-01-10 at 12:49 +0100, Stanislav Brabec wrote:
4. Enhance GConf:
The right fix IMO is that apps should parse the schema files
client-side, and don't install them to the gconf source at all.
See: http://www.gnome.org/projects/gconf/plans.html
This has a bunch of advantages,
On Tue, 2006-01-10 at 09:53 -0500, Havoc Pennington wrote:
On Tue, 2006-01-10 at 12:49 +0100, Stanislav Brabec wrote:
4. Enhance GConf:
The right fix IMO is that apps should parse the schema files
client-side, and don't install them to the gconf source at all.
See:
On Sat, 2005-12-24 at 19:35 -0500, William Lovaton wrote:
Hi, I was reading this thread without much interest but I really have to
say something: List View in Nautilus have been improving a lot and I
like the new developments so far, but it is very annoying when you
select a list item and it
On Tue, 2006-01-10 at 12:49 +0100, Stanislav Brabec wrote:
I have been searching for the reason, why GConf database contains
obsolete keys after correct package update. I found that it is a
concept problem, which affects many packaging systems:
GConf expects following update process:
-
On Tue, 2006-01-10 at 18:50 +0100, Jan de Groot wrote:
(ever wondered why debian waits
such a long time when installing a -data package? It's because of the DB
regeneration which fetches the DTD files from sourceforge).
Small point but Sarge has an XML catalogue so the DTD used is a local
On Tue, Jan 10, 2006, Rodney Dawes wrote:
I'm not sure what the best method for dpkg or other systems would be
though. Hopefully less nasty.
As I commented in the BTS, I don't think Debian or Ubuntu are affected.
--
Loïc Minier [EMAIL PROTECTED]
Current Earth status: NOT DESTROYED
Le mardi 10 janvier 2006 à 11:23 -0500, Rodney Dawes a écrit :
According to the RPM documentation, the way to handle this currently,
is unfortunately, to do the --makefile-uninstall-rule in the %pre of
the new package, if it's an upgrade, or in the %preun of the package,
in the event of
On Tue, 2006-01-10 at 17:46 +0100, Mark Rosenstand wrote:
See: http://www.gnome.org/projects/gconf/plans.html
This has a bunch of advantages, among them simplifying packaging.
Looks good. Does this mean that I should close my bug on the subject?
12 matches
Mail list logo
