[gentoo-user] freezing a package

[gentoo-user] freezing a package

[Michael P. Soulier]

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

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,
Mike
-- 
Michael P. Soulier <msoulier@digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-user] freezing a package

[Albert Hopkins]

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 it simpler to just remove nvidia-drivers from the world file?

Create an local overlay. Put the ebuild in there.

Re: [gentoo-user] freezing a package

[Michael P. Soulier]

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

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
-- 
Michael P. Soulier <msoulier@digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-user] freezing a package

[Dale]

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

:-)  :-)

Re: [gentoo-user] freezing a package

[Michael Higgins]

On Sat, 19 Dec 2009 19:01:03 -0500
"Michael P. Soulier" <msoulier@digitaltorque.ca> 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.

Yeah, that's too bad, because having your own overlay is a Good Thing,
IMO, in that it gives you some starting point for your own 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.

Why remove it from world file? Just put it in your overlay and mask any
later versions, like '>whateverpackage-N.NN-rN' (the version you want to
keep) in package.mask, I think.

> 
> 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

Except that it *will* be in the portage tree, in your personal overlay,
unless *you* delete your ebuild. ;-)

> downgrade.
> 

Cheers,

-- Michael Higgins

[gentoo-user] Re: freezing a package

[»Q«]

On Sat, 19 Dec 2009 19:01:03 -0500
"Michael P. Soulier" <msoulier@digitaltorque.ca> 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.

Unfortunately, the Gentoo overlays user's guide now focuses only on
using layman to get other people's overlays and no longer covers how
to set up a simple local overlay.  I guess there's enough info in
various manpages to piece it together, but here's a quick/dirty howto.

In make.conf:

  # to use some local ebuilds
  PORTDIR_OVERLAY="/usr/local/portage"

Or you can use any director(y|ies) you like, in a list separated by
spaces.

Then drop a copy of the ebuild into
$PORTDIR_OVERLAY/[category]/[packagename]/

Run `ebuild [ebuild file] manifest` to create the checksums for the
ebuild.  (Alternatively, I guess there's a way to copy the manifest
stuff from the portage tree.)

-- 
»Q«
     Kleeneness is next to Gödelness.

Re: [gentoo-user] freezing a package

[Alan McKinnon]

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 downgrade once that version is no longer in the portage
> > tree.
> >
> > Is it simpler to just remove nvidia-drivers from the world file?
> 
> 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 updated nvidia-drivers in portage which you might 
forget to mask

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] freezing a package

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 816 bytes --]

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 updated nvidia-drivers in portage which
> you might forget to mask

That's a good idea, but it will require some editing of the ebuild as
portage uses the name of the ebuild file to determine things like the
download URL and where it is unpacked. As the version is not going to
change again, you could replace the $P* references in the ebuild with
hard-coded names.

Overall, learning to use package.mask properly may be easier :)


-- 
Neil Bothwick

OPERATOR ERROR: Nyah, Nyah, Nyah, Nyah, Nyah!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] freezing a package

[Dale]

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 from the world file?
>
> Thanks,
> Mike
>   

I added this to the package.mask file:

 >x11-drivers/nvidia-drivers-173.14.20

That froze mine at that version.  Of course, keep in mind if say 
173.14.22 comes out, it won't upgrade then either.  If you upgrade your 
kernel later on and it requires a newer nvidia driver, you will have to 
edit that line.

I'm sure some other guru will have a better way tho.  ;-)

Dale

;-)  :-) 

Re: [gentoo-user] freezing a package

[Marcus Wanner]

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 simpler to just remove nvidia-drivers from the world file?
>>
>> Thanks,
>> Mike
>
> I added this to the package.mask file:
>
> >x11-drivers/nvidia-drivers-173.14.20
>
> That froze mine at that version.  Of course, keep in mind if say 
> 173.14.22 comes out, it won't upgrade then either.  If you upgrade 
> your kernel later on and it requires a newer nvidia driver, you will 
> have to edit that line.
>
> I'm sure some other guru will have a better way tho.  ;-)
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 version becuase portage got the latest 
96.x drivers, which were not masked.

For you, I would recommend
 >=x11-drivers/nvidia-drivers-174.00
Because that will get 173.14.22 if it comes out.

Marcus

Re: [gentoo-user] freezing a package

[Dale]

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 portage tree.
>>>
>>> Is it simpler to just remove nvidia-drivers from the world file?
>>>
>>> Thanks,
>>> Mike
>>
>> I added this to the package.mask file:
>>
>> >x11-drivers/nvidia-drivers-173.14.20
>>
>> That froze mine at that version.  Of course, keep in mind if say 
>> 173.14.22 comes out, it won't upgrade then either.  If you upgrade 
>> your kernel later on and it requires a newer nvidia driver, you will 
>> have to edit that line.
>>
>> I'm sure some other guru will have a better way tho.  ;-)
> 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 version becuase portage got the 
> latest 96.x drivers, which were not masked.
>
> For you, I would recommend
> >=x11-drivers/nvidia-drivers-174.00
> Because that will get 173.14.22 if it comes out.
>
> Marcus
>
>

Yep, that would work.  I knew someone would have a better idea.  I was 
expecting that little ~ thingy to be used tho.  ;-)

Dale

:-)  :-) 

Re: [gentoo-user] freezing a package

[Marcus Wanner]

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 version becuase portage got the 
>> latest 96.x drivers, which were not masked.
>>
>> For you, I would recommend
>> >=x11-drivers/nvidia-drivers-174.00
>> Because that will get 173.14.22 if it comes out.
> Yep, that would work.  I knew someone would have a better idea.  I was 
> expecting that little ~ thingy to be used tho.  ;-)
Actually, that one came right out of the Gentoo nVidia Guide...
http://www.gentoo.org/doc/en/nvidia-guide.xml#doc_chap2_sect1
*sheepish_look*

Marcus

Re: [gentoo-user] freezing a package

[Dale]

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 updated to the new version becuase portage got 
>>> the latest 96.x drivers, which were not masked.
>>>
>>> For you, I would recommend
>>> >=x11-drivers/nvidia-drivers-174.00
>>> Because that will get 173.14.22 if it comes out.
>> Yep, that would work.  I knew someone would have a better idea.  I 
>> was expecting that little ~ thingy to be used tho.  ;-)
> Actually, that one came right out of the Gentoo nVidia Guide...
> http://www.gentoo.org/doc/en/nvidia-guide.xml#doc_chap2_sect1
> *sheepish_look*
>
> Marcus
>
>
That guide most likely wasn't around when I started masking nvidia 
packages.  I sort of been around a good while here.  Feel like dirt 
sometimes.

Dale

:-)  :-)