| Summary: | nvidia-drivers (all versions) breaks moduledb on unmerge | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | ferret <ferret-bgo> |
| Component: | New packages | Assignee: | X11 External Driver Maintainers <x11-drivers> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ikelos, jakub, johnm, m.debruijne |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
I vote for changing linux-mod.eclass for using a seperate file for each package in a special directory for storing the moduledb. And no longer one file for all packages together. I think that's a good idea, but technically wouldn't solve this problem. If something gets unmerged it should be removed from the db, so that automatic kernel scripts like mine won't then reinstall things that have been removed. :) It would make the moduledb easier to deal with, though. Maybe you can start another bug for it? I'm not sure what splitting out the moduledb will achieve over the current situation with the current releases, however that being said I can see some benefit to scripted execution which has yet to be released. Please feel free to write up some kind of structure and post to a new bug if I dont get to it before. Fixed this in the nvidia-drivers and nvidia-legacy-drivers ebuilds... |
After unmerging nvidia-drivers (all the versions currently in portage), the moduledb doesn't get corrected. Patch is trivial, but unfortunately won't help anyone who has already installed, afaik, since the affected ebuild will be in their /var/db/pkg now. I've added the same 'if' condition as there is around other incantations of linux-mod_blah in this ebuild. --- nvidia-drivers-1.0.8774.ebuild 2006-09-02 11:24:14.000000000 +0000 +++ nvidia-drivers-1.0.8774.ebuild~ 2006-09-02 11:24:06.000000000 +0000 @@ -396,5 +396,9 @@ } pkg_postrm() { + if ! use x86-fbsd; then + linux-mod_pkg_postrm + fi + eselect opengl set --use-old xorg-x11 }