1 |
coalml@××××.io wrote: |
2 |
> Hi y'all new confused user regarding package management |
3 |
> |
4 |
> How do you guys manage and protect your packages? |
5 |
> Do you just put everything on world and end up with a huge world file? |
6 |
> Do you have basic system files on world and the rest you protect or omit? |
7 |
> Do you create new(personalised) files depending on category and |
8 |
> somehow link them in any of the above 3? |
9 |
> |
10 |
> It's just emerging everything you are not sure you will keep with -1 |
11 |
> seems cumbersome to me especially if at some point I want to transfer |
12 |
> to a new device and want to copy my settings over ,select what to keep |
13 |
> and discard the rest,depcleaning with pretend all the time seems |
14 |
> annoying on the long term as well so there should be lots of different |
15 |
> solutions from different people(at least thats what I think) |
16 |
> |
17 |
> I just think this is one of the things its better I learn now rather |
18 |
> than later and forum or wiki info is too "on-point" on a specific |
19 |
> situation so I thought I'd ask the userbase |
20 |
|
21 |
|
22 |
This is the way I've done it for a while, a couple decades. Once I get |
23 |
my new install done, everything installed that I want, I change the |
24 |
default for the emerge command and add --oneshot or -1. That way if I'm |
25 |
trying to work through a upgrade problem, I don't have to remember to |
26 |
use -1 to keep world clean. My default emerge options look like this: |
27 |
|
28 |
EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j5 |
29 |
--quiet-build=n -1 --unordered-display" |
30 |
|
31 |
Obviously, depending on CPU, available memory etc, you may want to |
32 |
adjust those to your case. The key points here, the -1, --with-bdeps y, |
33 |
--backtrack=100 and --keep-going options. 99% of the time, when I do my |
34 |
updates with the command emerge -auDN world, that gives me a easy |
35 |
upgrade. There may be exceptions at times but generally that works and |
36 |
gives me a stable system. |
37 |
|
38 |
Keep in mind, you don't have to worry about @system much if any. It's |
39 |
handled by the devs. As for world, you only keep in there the packages |
40 |
you use. When you update or install something new, emerge takes care of |
41 |
whatever depends on the package you want. As a example, if you want a |
42 |
full KDE install, you just emerge the kde meta package and it gets |
43 |
recorded in the world file. The emerge command will take care of all |
44 |
the other packages that depend on the meta package. That is a LOT of |
45 |
packages too. My biggest advice, if you find yourself fighting emerge |
46 |
to get things done, you're doing something wrong. These days, emerge |
47 |
-av <package> should work virtually 100% of the time. You may have to |
48 |
adjust USE flags or something but it should just work. |
49 |
|
50 |
Over the years, I've adjusted options until I got a easy update path. |
51 |
This works really, really well. I update once a week, usually Sunday |
52 |
night. Lately, I start late Saturday night or Sunday morning. That way |
53 |
I'm done and can update my backups Sunday night. |
54 |
|
55 |
Hope that helps. Welcome to Gentoo and the source of good heat, lots of |
56 |
compiling. lol |
57 |
|
58 |
Dale |
59 |
|
60 |
:-) :-) |