Michael P. Soulier wrote:
On 19/12/09 Albert Hopkins said:
Create an local overlay. Put the ebuild in there.
I'll need to read up on how. The section on overlays left me with the
impression that overlays were for experimental code, not for keeping private
copies of packages.
Anyway, I think I'll remove it from the world file, and mask it out, and look
into the overlay. At least it will be ignored when I emerge world.
I found that the > in the package.mask wasn't always enough though, as if I
used the --update argument to emerge and my version wasn't in the portage tree
anymore, emerge would get silly and offer to downgrade.
Mike
Hmmm, you may misunderstand something on this. You need to leave that
in there. The devs are not removing the packages from portage. Once
you mask it so that it will stick with the versions that work with your
card, you will be fine after that. The only updates will be the ones
that are needed.
I have a old FX-5200. After I put the line in my package.mask file, I
haven't seen a update in a good while. I did however have to update
when I updated my kernel a good while back. That is one reason to leave
that in the world file. If you update your kernel later on, you may
need to install a newer version of the nvidia drivers.
Unless the devs are removing the nvidia drivers from the tree, you
shouldn't need a overlay. You can do it that way but I'm not sure why
you need to.
Dale
:-) :-)
