From: "Jim Hall" <volunteer.jim@xxxxxxxxx>
On Thu, May 1, 2008 at 8:21 AM, Keith Brown <spamtrap@xxxxxxxxxxxx> wrote:
On Wed, Apr 30, 2008 at 8:08 PM, Paul Johnson <baloo@xxxxxxxxx> wrote:
I understand the being busy part too, and so don't blame him or really can
complain much, I just wouldn't say making updates every 3 or 4 versions as
timely either (since that is normally how often the debian Wine packages are
updated). Although, right now, 0.9.60 is in the unstable branch, and 0.9.59
was the version before that, so lately things are good.
Thanks for the more detailed info, folks. But apples & oranges, I think. I
get my deb's from budgetdedicated (for etch). Are you suggesting that I use
the sid one? if so, will it work with etch? If it will that would solve a
whole lot of problems!
From what I've seen, of the official debian packages, etch is
absolutely horrible, and is way out of date (0.9.25), unless you use the
backport. The backports tend to be the same release as Lenny, which
right now is 0.9.59. Under normal conditions for debian, Testing can be
as much as 8 releases out of date. I use sid, and so I go with the sid
packages, and really have no problem (for a desktop, really not much of
a reason to not use sid, since it is honestly far from unstable).
As far as the wine packages in the sid pool go, like I said, they're
normally a few versions out of date, but with the occasional spurt where
no releases are missed. Also, it usually is a bit before the packages
hit the pool (I remember .58 hit the package pool 8 days after the wine
dev team released .59). Looking at my package archive for this machine,
it went as follows .30, .31, 32, 33, .34, .39, .44, .47, .52, .53, .54,
.56, .58, .59, and .60. 30 versions of wine, with a total of 15 packages
in between.
