1 |
On 26/02/2022 22:14, Ramces Tampo-og Red wrote: |
2 |
> I see. I will be wary of my world file from now on. I'm glad that you |
3 |
> mentioned this now since I don't have that much packages installed yet |
4 |
> and I haven't played around with the system enough that there's a chance |
5 |
> that it might break. Knowing this is really handy since it might not be |
6 |
> apparent when things that shouldn't be added in the world file are being |
7 |
> added to the world file. |
8 |
|
9 |
If you think you might have been guilty of this, just edit your world |
10 |
file with vim or whatever, delete everything you don't recognise or you |
11 |
recognise as having been done for troubleshooting, and save it. It won't |
12 |
make any difference to your running system. Just be careful not to |
13 |
delete by accident stuff you really did want (although you could always |
14 |
re-emerge it). |
15 |
|
16 |
Then try an "emerge --depclean --pretend" and see what would be removed. |
17 |
Last time I did that, I then manually -C'd each package in turn - not |
18 |
least because I need to update my kernel an d depclean buggers that up |
19 |
if you're not careful ... always do an emerge, build new kernel, |
20 |
depclean quickly, in that order, with no sync in the middle! Otherwise |
21 |
you might end up cursing ... |
22 |
|
23 |
The other thing is, (and it's probably already been mentioned,) is make |
24 |
sure you know how to use package.use and package.accept. Don't add |
25 |
things like ~amd to our global settings, just add them freely for |
26 |
VERSIONED stuff in those directories. Then as updates come along, all |
27 |
your changes get left behind as "no longer necessary". |
28 |
|
29 |
I learnt this the hard way, I enabled ~amd for a package that had no |
30 |
stable versions, that required a new ~amd version of glibc, that then |
31 |
blocked any attempt to update my system! So there was a trail of |
32 |
messages on this list as I worked out how to fix the mess :-) |
33 |
|
34 |
By putting all this stuff in package.accept and package.use, I can keep |
35 |
track, and if the file is old it's probably out of date and ripe for |
36 |
deletion. I can just move it out the way, try an update, and if it blows |
37 |
up look what's in the file I've moved to see what I need to keep and |
38 |
what cruft can be deleted. |
39 |
|
40 |
Cheers, |
41 |
Wol |