| 1 |
Marcus Wanner wrote: |
| 2 |
> On 12/19/2009 10:27 AM, Dale wrote: |
| 3 |
>> Michael P. Soulier wrote: |
| 4 |
>>> If I want to freeze my nvidia-drivers because any upgrade will |
| 5 |
>>> abandon my |
| 6 |
>>> hardware, masking out newer versions doesn't seem to be enough as it |
| 7 |
>>> will also |
| 8 |
>>> offer to downgrade once that version is no longer in the portage tree. |
| 9 |
>>> |
| 10 |
>>> Is it simpler to just remove nvidia-drivers from the world file? |
| 11 |
>>> |
| 12 |
>>> Thanks, |
| 13 |
>>> Mike |
| 14 |
>> |
| 15 |
>> I added this to the package.mask file: |
| 16 |
>> |
| 17 |
>> >x11-drivers/nvidia-drivers-173.14.20 |
| 18 |
>> |
| 19 |
>> That froze mine at that version. Of course, keep in mind if say |
| 20 |
>> 173.14.22 comes out, it won't upgrade then either. If you upgrade |
| 21 |
>> your kernel later on and it requires a newer nvidia driver, you will |
| 22 |
>> have to edit that line. |
| 23 |
>> |
| 24 |
>> I'm sure some other guru will have a better way tho. ;-) |
| 25 |
> My package mask file reads |
| 26 |
> >=x11-drivers/nvidia-drivers-97.00 |
| 27 |
> Because I have a GEForce 3 from goodness knows when and need 96.x. |
| 28 |
> When something had ABI updates and the video driver was part of them, |
| 29 |
> the driver was updated to the new version becuase portage got the |
| 30 |
> latest 96.x drivers, which were not masked. |
| 31 |
> |
| 32 |
> For you, I would recommend |
| 33 |
> >=x11-drivers/nvidia-drivers-174.00 |
| 34 |
> Because that will get 173.14.22 if it comes out. |
| 35 |
> |
| 36 |
> Marcus |
| 37 |
> |
| 38 |
> |
| 39 |
|
| 40 |
Yep, that would work. I knew someone would have a better idea. I was |
| 41 |
expecting that little ~ thingy to be used tho. ;-) |
| 42 |
|
| 43 |
Dale |
| 44 |
|
| 45 |
:-) :-) |
Archives