1 |
On Mon, 10 Jul 2017 19:22:47 -0400 |
2 |
"William L. Thomson Jr." <wlt-ml@××××××.com> wrote: |
3 |
> |
4 |
> That part does not require it to resolve deps. Just check world file, |
5 |
> assuming its correct. Though could be thrown off if say gcc, or |
6 |
> another was in the world file. I think the profile or set would catch |
7 |
> that as it does now and generate a warning, regardless. |
8 |
|
9 |
Speaking of gcc in the world file. I think portage should STOP adding |
10 |
packages that are in the profile or a dep to world. If you merge a |
11 |
package as part of a set, I am pretty sure it does not get recorded to |
12 |
world, need to confirm, could be wrong. |
13 |
|
14 |
A rule for portage could be; |
15 |
|
16 |
- If the package is not in world and already installed. Do not add the |
17 |
package to world. If you are re-emerging a package already |
18 |
installed. You do not have to use the -1 option. |
19 |
|
20 |
I have polluted so many world files with system packages and/or |
21 |
dependencies I re-emerged directly without -1. Those IMHO should never |
22 |
have been recorded to that file. They were brought in by other things. |
23 |
Only things in my world should be packages merged directly, not from |
24 |
profile, set, or a dep. |
25 |
|
26 |
I will file a bug on that as well. |
27 |
|
28 |
-- |
29 |
William L. Thomson Jr. |