Donnie Berkholz wrote:
Simon Stelling wrote:
Donnie Berkholz wrote:
We are working to ensure the dependencies work as smoothly as possible,
but I expect there will be some issues since it's difficult to require
updates to all these optional drivers following an update to the server.
wouldn't !< atoms solve that problem?
The drivers cannot be upgraded until a newer server is installed. So
technically, this would allow things to work by forcing people to
unmerge all their drivers before upgrading, then remerge the new
versions. That's not a very desirable solution either, but do you think
it's the best one?
Thanks,
Donnie
Well the semantics of the blocker is that the new driver won't work with
the old server; is that true? Or just the old drivers won't work with
the new server?
I dislike using blocks to push users to fix issues; instead using guides
and such. But this is one of those things; how do you inform a bunch of
people, many who don't understand what an ABI is, to upgrade their
system in the proper order without them getting all pissed off at you
for lack of guidance ;)
My experience is limited only to #gentoo and the forums, but upgrade
snags of that sort generally hit both of those areas rather quickly,
making them easier to find. Of course this screams changelogs/news GLEP
material as well ;)
-Alec
--
gentoo-dev@gentoo.org mailing list
