-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 17/01/13 11:31 AM, Michael Orlitzky wrote: > On 01/17/2013 09:52 AM, Zac Medico wrote: >>> >>> I strongly believe that it shouldn't; nevertheless, it does. >> >> You can avoid this by adding --select=n to EMERGE_DEFAULT_OPTS. >> Then, if you want to add something to world, use --select (or -w >> in latest portage which isn't marked stable yet). > > This works by moving the badness from `emerge -u` to `emerge`. In > either case, to keep your world file accurate, you have to > remember to type an additional useless parameter every time you run > the command. When you're running depclean, you have to cross your > fingers and hope nobody forgot the magic --dont-break-world > parameter. > > I've "solved" this by installing every single package as a > dependency of something in our company repo. So we emerge > dev-util/mike_wants_to_be_able_to_run_strace_on_apache (depending > on strace) instead of dev-util/strace. This makes it obvious what > can be removed; we don't have normal packages listed in the world > file, so if you see one, it was a mistake. > > But it's not a very good solution, > > * It's a lot of work > > * I have to be the gatekeeper for every package install on every > server > > * It's stupid > >
... so what's the problem here, exactly? (a) 'emerge -u [pkg]' adds extra bits to @world when you don't want it to, or (b) you have users running 'emerge [pkg]' and you don't want THAT to end up in world either, or (c) you ONLY want 'emerge [pkg]' to end up adjusting world, AND only doing so for certain packages? It seems from your description you're trying to prevent all three issues.. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlD4MNIACgkQ2ugaI38ACPCPDwEAuiRjf33Y63iIDH0M5ruwo43u TdnYhkWD8Yz5Xq/WM7gA/jjea2n3dML1p5waCJqPp5F5vlLlLizXO7Js81/xjbVb =Pg74 -----END PGP SIGNATURE-----
