Re: gtk-engines photographed eating children

[Andrew Johnson <ajgenius ajgenius us>]

If there is no other good way to resolve this problem we can indeed do a
version bump. But I still see this as a problem with the package
versions in question. 

I am doing some searching and it seems this problem is exclusive to
debian & ubuntu, other distros I find which have broken out the engines
individually have all used the official engine versions as I would
expect.

So it would seem you and debian are the only people who ignore the
engine versions and use the fact it was also included in an other
package as an argument against doing so. I still consider this wrong and
self-defeating but if you aren't willing to change it I can't do
anything to really help EXCEPT up the version to 2.10.

Andrew

On Tue, 2005-01-25 at 06:09 +1100, Jeff Waugh wrote:
> <quote who="Andrew Johnson">
> 
> > On Tue, 2005-01-25 at 05:31 +1100, Jeff Waugh wrote:
> > > In an attempt to be perfectly clear: libmist.so is now (gtk-engines)
> > > 2.6.x where it was previously (gnome-themes) 2.9.x.
> > 
> > Ok and this is what bothers me. Mist is at version 0.10 + a few bug fixes.
> > IF you are using an aggregate package as an aggregate package then this
> > problem does not happen at all. If you are not using an aggregate package
> > as an aggregate package but un-aggregating them as it were, then why on
> > earth would you give them the version of the aggregate and not use the
> > individual versions.
> 
> The engines are shipped as separate binary packages from the same source
> package, similar to other packages in many distributions. Once you've
> aggregated mist into "module-x.y.z", there is no separate mist version
> number.