Re: gtk-engines photographed eating children

[Andrew Johnson <ajgenius ajgenius us>]

I think it just hit me what you are talking about by unique file
locations moving...

Let me take a stab at this - 

Old gnome themes provides lighthouseblue and depend on old gtk-engines.
which does not.

New gnome-themes does not provide lighthouseblue anymore, and depends on
new gtk engines which does.

So you cannot upgrade gnome-themes, because it depends on a new
gtk-engines which conflicts with the old gnome-themes. If you were too
force an upgrade, gtk-engines would upgrade LighthouseBlue, and then
gnome-themes upgrades, removing it again.  

So you have to remove the old gnome-themes, then upgrade gtk-engines,
then install gnome-themes, is that the gist of the problem?

Andrew

On Tue, 2005-01-25 at 02:12 +1100, Jeff Waugh wrote:
> Hey dudes,
> 
> The mish-mash of merging between gtk-engines/gnome-themes has imposed
> unfortunate side effects on distribution package(r)s.
> 
>  * gnome-themes has shifted from 2.8.x to 2.9.x
>  
>  * gtk-engines has shifted from 2.2.x to 2.6.x
> 
>  * a bunch of themes have moved from gnome-themes to gtk-engines, or more
>    importantly, a number of unique file locations have moved
> 
>  * current gtk-engines < gnome-themes
> 
> Thus, any distribution packaging the themes individually will not be able to
> upgrade higher version gnome-themes packages to lower version gtk-engines
> packages.
> 
> I still don't understand why we're stuck with two modules here... Can't all
> of these move into one or the other of gtk-engines or gnome-themes, so we
> can deprecate one and move forward?
> 
> Thanks,
> 
> - Jeff
> 
-- 
Andrew Johnson <ajgenius ajgenius us>