| 1 |
On Wednesday 24 June 2009 22:17:12 Mark Knecht wrote: |
| 2 |
> I really think this is what a personal overlay is for, but as I've |
| 3 |
> said for years, it's hard to build an overlay when you don't know what |
| 4 |
> needs to be in it until it's been removed. And yes, something has |
| 5 |
> removed these files, at least from my distfiles directory and I'm |
| 6 |
> pretty confident it wasn't me by hand because the machines all have |
| 7 |
> disk space which is the only reason I ever remove packages from there |
| 8 |
> by hand. There are still things lurking around in /var/db/pkgs or |
| 9 |
> whatever it's called so maybe I can learn how to create a personal |
| 10 |
> overlay form what's left and then go look elsewhere for other things |
| 11 |
> required. |
| 12 |
|
| 13 |
So why don't you do exactly that? |
| 14 |
|
| 15 |
I can't help but think when reading this thread that you are going round in |
| 16 |
circles, wondering if you should create a personal overlay, when you already |
| 17 |
know that the only possible solution IS a personal overlay. |
| 18 |
|
| 19 |
It's documented in the gentoo docs. Briefly: |
| 20 |
|
| 21 |
Create a directory somewhere for your stuff and include it in PORTDIR_OVERLAY |
| 22 |
in /etc/make.conf. If the current versions of ebuilds you need are currently |
| 23 |
installed, the ebuilds will be in /var/db/pkg so copy them to your overlay |
| 24 |
directory retaining the <category>/<package> structure. If not currently |
| 25 |
installed, get them from gentoo's cvs. Look inside each ebuild, see what it's |
| 26 |
DEPENDS are, make sure you have suitable ebuilds in your overlay. Rinse, |
| 27 |
repeat. It's fiddly, but not hard to do. |
| 28 |
|
| 29 |
Mask stuff using normal portage methods to make sure you don't upgrade to |
| 30 |
something incompatible. emerge world and let rip. |
| 31 |
|
| 32 |
Stop playing dixie with the idea and just do it, man! |
| 33 |
|
| 34 |
-- |
| 35 |
alan dot mckinnon at gmail dot com |
Archives