Re: gtk-engines photographed eating children
- From: Andrew Johnson <ajgenius ajgenius us>
- To: GNOME Desktop Hackers <desktop-devel-list gnome org>
- Cc: Jeff Waugh <jdub perkypants org>
- Subject: Re: gtk-engines photographed eating children
- Date: Mon, 24 Jan 2005 11:45:33 -0500
Ok on this I have to ask, why on earth would you have versioned this way
to begin with?
Each gtk engine has its own version, what happens if gnome-themes had
stopped providing one of these engines anyway(not just moved, removed),
would you have continued following gnome-themes versions for new
packages of the engines even as the discrepency between the official
number and gnome-themes got greater?
Just because the meta-source-package has changed doesn't mean the
version has.
Mist is what, at 0.7? This wouldn't have changed anything from that
perspective except maybe a patch number on the package...
I have no idea how to fix this problem, but I don't see that it has
anything to do with the move to gtk-engines except in that it exposed a
faulty way of numbering the engines to begin with.
Andrew
On Tue, 2005-01-25 at 03:27 +1100, Jeff Waugh wrote:
> <quote who="Sean Middleditch">
>
> > > ... but when themes move between differently-versioned source packages
> > > that are delivered as separate binary packages, things break.
> >
> > Maybe you should give a concrete example of packages (and their structure)
> > that this happens for...
>
> Was:
>
> gnome-themes 2.9.x -> gtk2-engines-mist 2.9.x
> gtk2-engines-thinice 2.9.x
>
> Now:
>
> gtk-engines 2.6.x -> gtk2-engines-mist 2.6.x
> gtk2-engines-thinice 2.6.x
>
> Limiting to two binary packages for simplicity's sake.
>
> - Jeff
>
--
Andrew Johnson <ajgenius ajgenius us>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]