| 1 |
> |
| 2 |
> You cannot really stay current on binaries but you can gradually |
| 3 |
> convert your |
| 4 |
> binary installation to a self-compiled one. You said above that |
| 5 |
> your *main* |
| 6 |
> machine was a laptop with insufficient harddisk space and CPU |
| 7 |
> power. That |
| 8 |
> implies you do have at least one other box. You could keep the |
| 9 |
> whole portage |
| 10 |
> tree, including the sources, on that other box and nfs mount it. |
| 11 |
> Alternatively, if that other box has got more CPU power, you can |
| 12 |
> compile the |
| 13 |
> whole thing there, tar everything (except the portage tree) up, |
| 14 |
> boot the |
| 15 |
> laptop from a livecd, get the tarball over and ... well ... untar |
| 16 |
> it. ;-) |
| 17 |
> That's what I usually do with a new box, so I don't have to start from |
| 18 |
> scratch. |
| 19 |
> |
| 20 |
bear in mind that this is more difficult if they two machines don't |
| 21 |
have the same architecture/use flags. be careful with this |
| 22 |
approach. If you optimize a compile for a p4 and try to run it on a |
| 23 |
p3...well, that might or might not work. |
| 24 |
-- |
| 25 |
gentoo-user@g.o mailing list |
Archives