1 |
On 07/10/2017 04:37 PM, William L. Thomson Jr. wrote: |
2 |
> On Mon, 10 Jul 2017 19:22:47 -0400 |
3 |
> "William L. Thomson Jr." <wlt-ml@××××××.com> wrote: |
4 |
>> |
5 |
>> That part does not require it to resolve deps. Just check world file, |
6 |
>> assuming its correct. Though could be thrown off if say gcc, or |
7 |
>> another was in the world file. I think the profile or set would catch |
8 |
>> that as it does now and generate a warning, regardless. |
9 |
> |
10 |
> Speaking of gcc in the world file. I think portage should STOP adding |
11 |
> packages that are in the profile or a dep to world. If you merge a |
12 |
> package as part of a set, I am pretty sure it does not get recorded to |
13 |
> world, need to confirm, could be wrong. |
14 |
> |
15 |
> A rule for portage could be; |
16 |
> |
17 |
> - If the package is not in world and already installed. Do not add the |
18 |
> package to world. If you are re-emerging a package already |
19 |
> installed. You do not have to use the -1 option. |
20 |
> |
21 |
> I have polluted so many world files with system packages and/or |
22 |
> dependencies I re-emerged directly without -1. Those IMHO should never |
23 |
> have been recorded to that file. They were brought in by other things. |
24 |
> Only things in my world should be packages merged directly, not from |
25 |
> profile, set, or a dep. |
26 |
> |
27 |
> I will file a bug on that as well. |
28 |
> |
29 |
Whether Portage adds a package to a set or world file is dependent on |
30 |
how you invoke emerge. Some people (like me) include sets as part of |
31 |
their world, via /var/lib/portage/world_sets . At that point, sets added |
32 |
to that file are basically treated as the world package list. |
33 |
|
34 |
If gcc or other @system packages end up in your world, it's not |
35 |
Portage's fault. If you don't want a package added to a set or world, |
36 |
you'll need to use the -1 (--oneshot) option. I added it to my default |
37 |
emerge options in make.conf for exactly that reason (clean world); |
38 |
though, I have to be careful and make sure packages I care about are in |
39 |
a set somewhere or --depclean will wipe'em out. In short, Portage won't |
40 |
stop you from shooting yourself in the foot. |
41 |
|
42 |
If you decide you want to add a package to world without re-merging it, |
43 |
-n (--noreplace) will do the job. |
44 |
|
45 |
I'm not sure if eix-test-obsolete (from app-portage/gentoolkit) will |
46 |
catch a @system atom inside a set/world file, but that's where I'd |
47 |
expect such a notification to come from. The tool can help clean up |
48 |
unneeded entries in /etc/portage files, and would be a good fit for this |
49 |
particular issue. |
50 |
|
51 |
That said, having helpful messages is a good addition, but needs to be |
52 |
done in a way that is unambiguous and gives the user a clear solution. |
53 |
|
54 |
Hope this helps, |
55 |
|
56 |
zlg |
57 |
-- |
58 |
Daniel Campbell - Gentoo Developer |
59 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
60 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |