| 1 |
On 01/09/2014 05:43 PM, Tom Wijsman wrote: |
| 2 |
|
| 3 |
> you might want to start over by |
| 4 |
> removing /var/lib/layman and emerging it again... |
| 5 |
|
| 6 |
Aha! Bitrot is not our friend :) |
| 7 |
|
| 8 |
I was running a very old version of layman, which yesterday I updated by |
| 9 |
emerging a new layman. |
| 10 |
|
| 11 |
Here's the catch: my old layman created /var/lib/layman and the old |
| 12 |
make.conf file, and (apparently) the new layman ebuild won't delete |
| 13 |
the old files, *and* also doesn't print this important message, which |
| 14 |
is what I needed most: |
| 15 |
|
| 16 |
>>> Installing (1 of 1) app-portage/layman-2.0.0-r2 |
| 17 |
* Running layman-updater... |
| 18 |
* Creating layman's make.conf file <========= Note :) |
| 19 |
* You are now ready to add overlays into your system. |
| 20 |
* |
| 21 |
* layman -L |
| 22 |
|
| 23 |
BTW, I find I need to run layman -S before I try layman -a, otherwise |
| 24 |
layman says there is no such overlay. |
| 25 |
|
| 26 |
Thanks to Peter and Tanstaafl for pointing out that the format |
| 27 |
of make.conf has changed from my previous version of layman. |
| 28 |
|
| 29 |
Now I'll see if I can get 'mate' working... |
Archives