1 |
Wol <antlists@××××××××××××.uk> writes: |
2 |
> On 26/02/2022 22:14, Ramces Tampo-og Red wrote: |
3 |
>> I see. I will be wary of my world file from now on. I'm glad that you |
4 |
>> mentioned this now since I don't have that much packages installed yet |
5 |
>> and I haven't played around with the system enough that there's a chance |
6 |
>> that it might break. Knowing this is really handy since it might not be |
7 |
>> apparent when things that shouldn't be added in the world file are being |
8 |
>> added to the world file. |
9 |
> |
10 |
> If you think you might have been guilty of this, just edit your world |
11 |
> file with vim or whatever, delete everything you don't recognise or you |
12 |
> recognise as having been done for troubleshooting, and save it. It won't |
13 |
> make any difference to your running system. Just be careful not to |
14 |
> delete by accident stuff you really did want (although you could always |
15 |
> re-emerge it). |
16 |
> |
17 |
|
18 |
Coming from a binary-based distribution, this stuff is just pure magic |
19 |
to me. I feel like I'm just now learning how to actually manage my |
20 |
system. This made me think, would it be possible to trim my world file |
21 |
and sort them into sets? I'm digging the possibility of being able to |
22 |
only update groups of packages that I want to. |
23 |
|
24 |
I've been struggling with updates lately since I've emerged qutebrowser |
25 |
and updates to qtwebengine is brutal to my X200. I haven't set-up distcc |
26 |
yet and the hard drive in this poor thing isn't enough to cover for a |
27 |
decently sized ccache. |
28 |
|
29 |
So I'm wondering whether it would be feasible to just move some of the |
30 |
contents of the world file into sets and just manage the packages that |
31 |
way. |
32 |
|
33 |
> Then try an "emerge --depclean --pretend" and see what would be removed. |
34 |
> Last time I did that, I then manually -C'd each package in turn - not |
35 |
> least because I need to update my kernel an d depclean buggers that up |
36 |
> if you're not careful ... always do an emerge, build new kernel, |
37 |
> depclean quickly, in that order, with no sync in the middle! Otherwise |
38 |
> you might end up cursing ... |
39 |
> |
40 |
|
41 |
Yeah, I can see why that would be a problem if you did a sync in the |
42 |
middle. |
43 |
|
44 |
> The other thing is, (and it's probably already been mentioned,) is make |
45 |
> sure you know how to use package.use and package.accept. Don't add |
46 |
> things like ~amd to our global settings, just add them freely for |
47 |
> VERSIONED stuff in those directories. Then as updates come along, all |
48 |
> your changes get left behind as "no longer necessary". |
49 |
> |
50 |
> I learnt this the hard way, I enabled ~amd for a package that had no |
51 |
> stable versions, that required a new ~amd version of glibc, that then |
52 |
> blocked any attempt to update my system! So there was a trail of |
53 |
> messages on this list as I worked out how to fix the mess :-) |
54 |
> |
55 |
> By putting all this stuff in package.accept and package.use, I can keep |
56 |
> track, and if the file is old it's probably out of date and ripe for |
57 |
> deletion. I can just move it out the way, try an update, and if it blows |
58 |
> up look what's in the file I've moved to see what I need to keep and |
59 |
> what cruft can be deleted. |
60 |
> |
61 |
|
62 |
Oh man, I did this once! I added ~amd64 as a global variable and |
63 |
everything updated. I didn't realize the folly of what I did until I saw |
64 |
that gcc is being rebuilt. I think I've gone a little bit wiser since |
65 |
then (hopefully). |
66 |
|
67 |
> Cheers, |
68 |
> Wol |
69 |
> |
70 |
|
71 |
Thank you for the really helpful tips! |
72 |
|
73 |
Cheers! |
74 |
|
75 |
-- |
76 |
. * + |
77 |
+ Ang kalayaan ay dili gihatag, ini'y giabot. |
78 |
* + {gopher,gemini}://kalayaan.xyz * |
79 |
. C4AE 5D53 46A0 01DF 6E92 CB46 92D7 9FBB AB9F 3E37 . |