After messing up and accidentally unmerging a python, I untarred it manually and then put it in /usr/portage/packages/dev-lang
Now I'm trying to run emerge -K to make sure all the files are recorded, and I've supplied FEATURES="-protect-owned -collision-protect" both on the command line and in make.conf but emerge is still doing a collision check even though I told it not to.
Steps to Reproduce:
1. see description
scans for collisions
doesn't scan for collisions.
Created attachment 239601 [details]
emerge --info portage
There's a error message that's shown for any collisions, regardless of whether protect-owned or collision-protect are enabled. I guess we can add a way to disable the warning, but it's really not recommended to disable protect-owned anyway.
True, generally that is the case.
However, there is a special case where you need to manually untar a package to fix a broken portage. This has a side effect of creating orphans that you know will be recorded by an emerge -K of the same package.
In this special case, and most likely others, even checking for collisions is superfluous, in which case specifying -collision-protect and -protect-owned together should be allowed to instruct portage not to do a collision check.
Mostly because checking for collisions that the admin already knows are bogus is a waste of CPU time.
It's actually the owners lookup that wastes time, while the collision check is relatively quick. So, I'll go ahead and disable the owners lookup, while leaving the quick collision check in place. Also, the owners lookup is optimized for small numbers of files, so I plan to make it use a different algorithm for larger numbers of files.
(In reply to comment #4)
> Also, the owners lookup is
> optimized for small numbers of files, so I plan to make it use a different
> algorithm for larger numbers of files.
This part is fixed here:
(In reply to comment #4)
> It's actually the owners lookup that wastes time, while the collision check is
> relatively quick. So, I'll go ahead and disable the owners lookup, while
> leaving the quick collision check in place.
The owners lookup is disabled here:
This is in 2.2_rc68, but I'll leave this bug open until it's in an unmasked version.
This is fixed in 2.1.9.
(In reply to comment #8)
> This is fixed in 2.1.9.
Just for saving anyone else a painful moment of smacking oneself to the forehead:
as of today (27.09.2010) 2.1.9 is still masked and you need to use ACCEPT_KEYWORDS to actually install it.