On Mon, Mar 05, 2007 at 04:46:09PM +0100, Tomasz Torcz wrote:
> On Mon, Mar 05, 2007 at 01:13:26AM -0600, Matt Mackall wrote:
> > That's not the point. The point is that Debian/unstable as of _this
> > morning_ doesn't work. For reference, I'm running both the latest
> > releases of both hal (0.5.8.1-6.1) and network-manager (0.6.4-6). And
> > there are people telling me I need a copy of HAL out of git that
> > hasn't even been released for Debian to package. Debian isn't the
> > problem here.
>
> hal 0.5.9-rc1 (released, not from git) should work. It will be
> problably released soon and picked by sane distributions. Debian is very
> irritating corner case.
As of right now, Fedora Core 6 has hal-0.5.8.1-6.fc6. This is also
too old. Please, stop claiming that Debian unstable is some corner
case. No one is talking about Debian stable here. No one is talking
about the Enterprise versions of Red Hat or SuSE (you'd find them just
as irritating with modern kernels). Debian unstable tracks released
code as fast or faster than Fedora and OpenSuSE. They all keep up with
releases.
But the last release of hal is 0.5.8.1. _Release_, not "release
candidate". You can't break that. You can't break it for a while, if
you want a sane deprecation schedule. These are userspace interfaces.
Matt is absolutely correct that you should't deprecate a
userspace<->kernel interface before you've even provided a release of
the tool that detects the change!
Joel
--
"When ideas fail, words come in very handy."
- Goethe
Joel Becker
Principal Software Developer
Oracle
E-mail: [EMAIL PROTECTED]
Phone: (650) 506-8127
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
