| 1 |
On 26/09/2015 18:47, Neil Bothwick wrote: |
| 2 |
>>> The other one is portage snapshots. |
| 3 |
>> > |
| 4 |
>> > That sounds like something I should learn about. |
| 5 |
> See above re backups, it's just a tarball of the portage tree. |
| 6 |
|
| 7 |
|
| 8 |
Just beware of one thing. Syncing the tree and then *using* it is often |
| 9 |
a one-way street, especially if deps got in the mix. |
| 10 |
|
| 11 |
Portage can't unwind the most recent merges so you have to rely on a |
| 12 |
side-effect - hoping that portage will notice your package of X isn't in |
| 13 |
the current tree then will downgrade it to one that is. |
| 14 |
|
| 15 |
-- |
| 16 |
Alan McKinnon |
| 17 |
alan.mckinnon@×××××.com |
Archives