1 |
On Mon, Aug 29, 2016 at 4:12 PM, Ian Zimmerman <itz@×××××××.net> wrote: |
2 |
> On 2016-08-29 20:08, Neil Bothwick wrote: |
3 |
> |
4 |
>> Surely the addition of X, and maybe kde or gnome, to your USE flags is |
5 |
>> what is causing so many packages to be pulled in by @system. |
6 |
>> |
7 |
>> I found something similar when building a new system recently, @system |
8 |
>> pulled in X and a shedload of dependencies. Switching to a non-desktop |
9 |
>> profile meant far fewer packages were needed to get a basic system. |
10 |
> |
11 |
> Can you safely do this (change profile) on an existing system, and how? |
12 |
> Will it affect @world, and more generally, will it cause the next update |
13 |
> do work that would otherwise not be done? |
14 |
> |
15 |
|
16 |
Switching profile isn't a big deal as long as you don't mess with the |
17 |
toolchain. You can't just go between multilib and non-multilib, for |
18 |
example. However going from desktop to base is trivial. |
19 |
|
20 |
Now, if you switch from desktop to base, rebuild half your system, |
21 |
then switch back to desktop, then of course emerge will want to |
22 |
rebuild half your system again. Or if you go from systemd to |
23 |
non-systemd and have systemd as your init, then obviously you'll get a |
24 |
surprise on reboot if you don't change your kernel command line. |
25 |
|
26 |
Changing profiles is no different from changing a whole bunch of USE |
27 |
flags for the most part. |
28 |
|
29 |
In general you should set your profile/flags to whatever you want them |
30 |
at and leave it there, unless you're trying to fix some kind of |
31 |
circular dependency issue. You're not going to save any time by |
32 |
dropping flags and then re-enabling them. |
33 |
|
34 |
-- |
35 |
Rich |