On Sun, 20 Dec 2009 09:03:19 +0200, Alan McKinnon wrote:
> > Create an local overlay. Put the ebuild in there.
>
> I'd also rename the ebuild to something like
>
> my-nvidia-drivers
>
> That way it becomes a completely new app from portage's point of view
> and therefore not subject to update
On Saturday 19 December 2009 17:18:30 Albert Hopkins wrote:
> On Sat, 2009-12-19 at 10:12 -0500, Michael P. Soulier wrote:
> > If I want to freeze my nvidia-drivers because any upgrade will abandon my
> > hardware, masking out newer versions doesn't seem to be enough as it will
> > also offer to do
On Sat, 19 Dec 2009 19:01:03 -0500
"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 keep
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,
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 worl
Marcus Wanner wrote:
On 12/19/2009 12:37 PM, Dale wrote:
Marcus Wanner wrote:
My package mask file reads
>=x11-drivers/nvidia-drivers-97.00
Because I have a GEForce 3 from goodness knows when and need 96.x.
When something had ABI updates and the video driver was part of
them, the driver was
On 12/19/2009 12:37 PM, Dale wrote:
Marcus Wanner wrote:
My package mask file reads
>=x11-drivers/nvidia-drivers-97.00
Because I have a GEForce 3 from goodness knows when and need 96.x.
When something had ABI updates and the video driver was part of them,
the driver was updated to the new ve
Marcus Wanner wrote:
On 12/19/2009 10:27 AM, Dale wrote:
Michael P. Soulier wrote:
If I want to freeze my nvidia-drivers because any upgrade will
abandon my
hardware, masking out newer versions doesn't seem to be enough as it
will also
offer to downgrade once that version is no longer in the
On 12/19/2009 10:27 AM, Dale wrote:
Michael P. Soulier wrote:
If I want to freeze my nvidia-drivers because any upgrade will
abandon my
hardware, masking out newer versions doesn't seem to be enough as it
will also
offer to downgrade once that version is no longer in the portage tree.
Is it s
Michael P. Soulier wrote:
If I want to freeze my nvidia-drivers because any upgrade will abandon my
hardware, masking out newer versions doesn't seem to be enough as it will also
offer to downgrade once that version is no longer in the portage tree.
Is it simpler to just remove nvidia-drivers fr
On Sat, 2009-12-19 at 10:12 -0500, Michael P. Soulier wrote:
> If I want to freeze my nvidia-drivers because any upgrade will abandon my
> hardware, masking out newer versions doesn't seem to be enough as it will also
> offer to downgrade once that version is no longer in the portage tree.
>
> Is
If I want to freeze my nvidia-drivers because any upgrade will abandon my
hardware, masking out newer versions doesn't seem to be enough as it will also
offer to downgrade once that version is no longer in the portage tree.
Is it simpler to just remove nvidia-drivers from the world file?
Thanks,
12 matches
Mail list logo
