On Wed, 05 Apr 2017 12:53:43 -0400, Alan Grimes wrote:

> I hit the "view raw" link and used save as... I then copied it into the
> "files" subdirectoy and portage threw a hissy fit and refused to do
> anything because letting the user patch a package is simply
> unthinkable!!! A mere USER, applying a custom patch to one of our
> immaculate packages on HIS OWN COMPUTER??!?!?! UNTHINKABLE!!!

Yes, just let anyone modify files in your portage tree and have portage
ignore any such changes, very secure.

> So it
> doesn't flash a warning, or a "are you sure?????", it just barfs and
> quits.  I then mv ..'d it. and portage completely ignores the file. 
> Doesn't match any of the versions I have anyway.

One of the problems with top posting is it makes it much easier to reply
to an email without properly reading it. The text you quoted tells you
exactly how to apply user patches, and they don't go in the portage tree.
 
> Which gets me back to how wise I was for version-freezing myself at
> 4.6.7...
> 
> And yes, I am continuing to call my Ryzen 1800x "tortoise". =P
> 
> ###
> 
> tortoise nvidia-drivers # ls -l
> total 268
> -rw-r--r-- 1 root    root    10392 Apr  5 12:42 378.09-4.10-rc8.patch
> drwxr-xr-x 2 portage portage  4096 Apr  5 12:43 files
> -rw-r--r-- 1 portage portage 32304 Mar 30 03:29 Manifest
> -rw-r--r-- 1 portage portage  1250 Mar 30 03:27 metadata.xml
> -rw-r--r-- 1 portage portage 16490 Feb 28 14:50
> nvidia-drivers-173.14.39-r1.ebuild
> -rw-r--r-- 1 portage portage 16476 Feb 28 14:50
> nvidia-drivers-173.14.39-r2.ebuild
> -rw-r--r-- 1 portage portage 13327 Feb 28 14:50
> nvidia-drivers-304.134.ebuild
> -rw-r--r-- 1 portage portage 13412 Feb 28 14:50
> nvidia-drivers-304.134-r1.ebuild
> -rw-r--r-- 1 portage portage 13410 Mar 30 03:29
> nvidia-drivers-304.135.ebuild
> -rw-r--r-- 1 portage portage 14460 Feb 28 14:50
> nvidia-drivers-340.101.ebuild
> -rw-r--r-- 1 portage portage 14525 Feb 28 14:50
> nvidia-drivers-340.101-r1.ebuild
> -rw-r--r-- 1 portage portage 14523 Mar 30 03:29
> nvidia-drivers-340.102.ebuild
> -rw-r--r-- 1 portage portage 15425 Feb 28 14:50
> nvidia-drivers-375.26.ebuild -rw-r--r-- 1 portage portage 15613 Feb 28
> 14:50 nvidia-drivers-375.26-r3.ebuild
> -rw-r--r-- 1 portage portage 15611 Mar 30 03:29
> nvidia-drivers-375.39.ebuild -rw-r--r-- 1 portage portage 15676 Mar 30
> 03:29 nvidia-drivers-378.13.ebuild -rw-r--r-- 1 portage portage 14755
> Feb 28 14:50 nvidia-drivers-96.43.23-r1.ebuild
> tortoise nvidia-drivers #
> 
> 
> 
> 
> Fabio Scaccabarozzi wrote:
> >
> > You can drop it in /etc/portage/patches/x11-drivers/nvidia-drivers
> > folder, portage should take care of the rest when you emerge the
> > package. You should see 3 lines near the prepare phase, before the
> > configure phase, saying something like "applying user patches from...
> > Applying <patch>...Done applying user patches"
> >
> >
> > Il mer 5 apr 2017, 17:40 Alan Grimes <alonz...@verizon.net
> > <mailto:alonz...@verizon.net>> ha scritto:
> >
> >     Looks like a good patch but can you link to instructions for
> > applying this patch?
> >
> >
> >     Fabio Scaccabarozzi wrote:  
> >     >
> >     > Hi Alan,
> >     >
> >     > That is expected with 4.10 kernels.
> >     > You can grab a patch from my /etc/portage repository:
> >     >  
> >     
> > https://github.com/fsvm88/gentoo-portage_etc/blob/master/patches/x11-drivers/nvidia-drivers/378.09-4.10-rc8.patch
> >   
> >     >
> >     > I took it from the NVidia forums, you can also find it there, I
> >     > just rebased it for portage.
> >     >  
> >
> >
> >     --
> >     Strange Game.
> >     The only winning move is not to play.
> >
> >     Powers are not rights.
> >
> >  
> 
> 




-- 
Neil Bothwick

NOTICE:
  --  THE ELEVATORS WILL BE OUT OF ORDER TODAY  --
  (The nearest working elevators are in the building
   across the street.)

Attachment: pgpvSPvO0uqsN.pgp
Description: OpenPGP digital signature

Reply via email to