Bug#731654: Blacklist resolved

[ael]

On Tue, Dec 10, 2013 at 06:36:01PM +0100, Andreas Beckmann wrote:
> Can I find this somewhere in the logfiles you sent previously?

First, apologies for the long silence. 

My hypothesis was just speculation rather than analysis or knowledge, I
fear :-(

> The current and legacy driver packages are intentionally co-installable
> to support e.g. live-systems. And the current driver gets the highest
> priority in the alternatives, of course.

That is what I had not appreciated. I agree it is tricky.

> If you have any ideas how to improve the packaging and/or documentation
> for the legacy drivers, I'd like to hear them - especially from a user
> who got into the trouble :-)

I just did an aptitude full-upgrade, and all the messages from the few
hundred new packages flashed by without any chance of reading them.
Since I do that regularly and it is very rare for there to be a problem,
I don't expect to need to read the messages even if it were possible.
Of course, you will know that.

Thereafter, it was a matter of changing to the legacy packages and I was
unclear on what constituted a full set, and the relationship to the
standard versions. 

> Maybe adding another metapackage that depends on the legacy driver and
> conflicts with all the other drivers - would this help? How should it be
> called? Or should the "co-installable" metapackage
> nvidia-legacy-173xx-driver be renamed (ito what?) and replaced by a
> "only-173xx" meta-package (named nvidia-legacy-173xx-driver)?

I will have to give that some thought after the holiday season.
Apologies again for the long delayed reply.

ael