| 1 |
On Sat, 19 Dec 2009 19:01:03 -0500 |
| 2 |
"Michael P. Soulier" <msoulier@×××××××××××××.ca> wrote: |
| 3 |
|
| 4 |
> On 19/12/09 Albert Hopkins said: |
| 5 |
> |
| 6 |
> > Create an local overlay. Put the ebuild in there. |
| 7 |
> |
| 8 |
> I'll need to read up on how. The section on overlays left me with the |
| 9 |
> impression that overlays were for experimental code, not for keeping |
| 10 |
> private copies of packages. |
| 11 |
|
| 12 |
Yeah, that's too bad, because having your own overlay is a Good Thing, |
| 13 |
IMO, in that it gives you some starting point for your own packages. |
| 14 |
|
| 15 |
> |
| 16 |
> Anyway, I think I'll remove it from the world file, and mask it out, |
| 17 |
> and look into the overlay. At least it will be ignored when I emerge |
| 18 |
> world. |
| 19 |
|
| 20 |
Why remove it from world file? Just put it in your overlay and mask any |
| 21 |
later versions, like '>whateverpackage-N.NN-rN' (the version you want to |
| 22 |
keep) in package.mask, I think. |
| 23 |
|
| 24 |
> |
| 25 |
> I found that the > in the package.mask wasn't always enough though, |
| 26 |
> as if I used the --update argument to emerge and my version wasn't in |
| 27 |
> the portage tree anymore, emerge would get silly and offer to |
| 28 |
|
| 29 |
Except that it *will* be in the portage tree, in your personal overlay, |
| 30 |
unless *you* delete your ebuild. ;-) |
| 31 |
|
| 32 |
> downgrade. |
| 33 |
> |
| 34 |
|
| 35 |
Cheers, |
| 36 |
|
| 37 |
-- Michael Higgins |
Archives