Executing rpm command of ebuild utility finishes on creating package in tempdir. For example: # ebuild /usr/portage/gentoo/dev-php/tcpdf/tcpdf-5.9.149.ebuild rpm … Processing files: tcpdf-5.9.149-r0.x86_64 Provides: tcpdf = 5.9.149-r0 tcpdf(x86-64) = 5.9.149-r0 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Checking for unpackaged file(s): /usr/libexec/rpm//check-files /var/tmp/portage/dev-php/tcpdf-5.9.149/image Wrote: /var/tmp/portage/dev-php/tcpdf-5.9.149/temp/rpmbuild/RPMS/x86_64/tcpdf-5.9.149-r0.x86_64.rpm … Reproducible: Always Steps to Reproduce: Use ebuild utility to build an rpm package (for quoted example, or for any other). Actual Results: Find process finished on success build of package in private default permissions temporary directory. Expected Results: I expect built package to be copied in a proper /usr/src/rpm/ subdirectory (for quoted example /usr/src/rpm/RPMS/x86_64) with autoclean of package's WORKDIR. Ideally, for future analyse, I'll be happy to see not only package itself, but also it's spec-file in /usr/src/rpm/SPECS. Also it may be useful, to add into eclean-pkg utility feature of check existance of rpm-packages and if present — check on outdated ones, if find — echo list (autoremove here to my mind is not correct).
Please post the output of this command: portageq envvar RPMDIR
(In reply to Zac Medico from comment #1) > Please post the output of this command: > > portageq envvar RPMDIR Ops… Excuse me. $ portageq envvar RPMDIR /usr/portage/rpm ls /usr/portage/rpm/ dev-php/ sys-libs/ ls /usr/portage/rpm/dev-php/ tcpdf-5.9.149-r0.rpm* I was confused with: $ file /usr/src/rpm /usr/src/rpm: directory $ equery b /usr/src/rpm * Searching for /usr/src/rpm ... app-arch/rpm-4.11.0.1 (/usr/src/rpm) Also I find not completely correct: 1: $ ls -l /var/tmp/portage/dev-php/tcpdf-5.9.149/temp/rpmbuild/RPMS/x86_64/ -rw-rw-r-- 1 portage portage 11639256 окт. 17 10:25 tcpdf-5.9.149-r0.x86_64.rpm (file not executable, arch-type (present, although incorrect, asked in bug #488320, maybe invalid) in suffix) 2: $ ls -l /usr/portage/rpm/dev-php/ -rwxr-xr-x 1 root root 11639256 окт. 17 10:25 tcpdf-5.9.149-r0.rpm* (arch-type is lost, file became executable) And the last question: I find not clear portage's behaviour: it neither cleans temporary dirs nor warns about it. P.S. Find spec file (/var/tmp/portage/dev-php/tcpdf-5.9.149/temp/tcpdf-5.9.149.spec) is yet rather poor, but may be useful for future.
I was confised with searching packages in the place I've find them after first builds.