1 |
On Sun, 20 Dec 2009 09:03:19 +0200, Alan McKinnon wrote: |
2 |
|
3 |
> > Create an local overlay. Put the ebuild in there. |
4 |
> |
5 |
> I'd also rename the ebuild to something like |
6 |
> |
7 |
> my-nvidia-drivers |
8 |
> |
9 |
> That way it becomes a completely new app from portage's point of view |
10 |
> and therefore not subject to updated nvidia-drivers in portage which |
11 |
> you might forget to mask |
12 |
|
13 |
That's a good idea, but it will require some editing of the ebuild as |
14 |
portage uses the name of the ebuild file to determine things like the |
15 |
download URL and where it is unpacked. As the version is not going to |
16 |
change again, you could replace the $P* references in the ebuild with |
17 |
hard-coded names. |
18 |
|
19 |
Overall, learning to use package.mask properly may be easier :) |
20 |
|
21 |
|
22 |
-- |
23 |
Neil Bothwick |
24 |
|
25 |
OPERATOR ERROR: Nyah, Nyah, Nyah, Nyah, Nyah! |