localhost ~ # emerge slocate
Calculating dependencies... done!
>>> Verifying ebuild Manifests...
>>> Emerging (1 of 1) sys-apps/slocate-3.1-r1 to /
* slocate-3.1.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking slocate-3.1.tar.gz ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking slocate-3.1.tar.gz to /var/tmp/portage/sys-apps/slocate-3.1-r1/work
* Applying slocate-3.1-build.patch ... [ ok ]
* Applying slocate-3.1-incompat-warning.patch ... [ ok ]
* Applying slocate-3.1-cron.patch ... [ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-apps/slocate-3.1-r1/work/slocate-3.1 ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-apps/slocate-3.1-r1
>>> Install slocate-3.1-r1 into /var/tmp/portage/sys-apps/slocate-3.1-r1/image/ category sys-apps
>>> Completed installing slocate-3.1-r1 into /var/tmp/portage/sys-apps/slocate-3.1-r1/image/
ecompressdir: bzip2 -9 usr/share/man
* QA Notice: Pre-stripped files found:
* /var/tmp/portage/sys-apps/slocate-3.1-r1/image/usr/bin/slocate
* checking 13 files for package collisions
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at http://bugs.gentoo.org unless you report exactly which
* two packages install the same file(s). Once again, please do NOT file
* a bug report unless you have completely understood the above message.
*
* package sys-apps/slocate-3.1-r1 NOT merged
*
* Detected file collision(s):
*
* /usr/bin/updatedb
* /usr/bin/locate
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
* Messages for package sys-apps/slocate-3.1-r1:
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at http://bugs.gentoo.org unless you report exactly which
* two packages install the same file(s). Once again, please do NOT file
* a bug report unless you have completely understood the above message.
*
* package sys-apps/slocate-3.1-r1 NOT merged
*
* Detected file collision(s):
*
* /usr/bin/updatedb
* /usr/bin/locate
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).