rpm generation on emerge copies the source tars and a fake SPEC for RPM to go through his normal unpack/compile/install process but doesn't instruct rpm to clean after himself, leaving all those files behind after the rpm is generated and which are useless (as the build and sources are fake anyway) aditionally the last step is to copy the generated rpm on /usr/src/redhat/RPMS/`uname -m`/ to the package repository for emerge which is also left as a duplicate, eventhough in this last case it might be assumed to be to be consistent with RPMs' expected behaviour. Reproducible: Always Steps to Reproduce: 1. ebuild file.ebuild rpm 2. find /usr/src/redhat -type f 3. Actual Results: /usr/src/redhat/BUILD/ and /usr/src/redhat/SOURCES contain files copied from the portage tree which are of no use anymore Expected Results: remove the BUILD and SOURCES files which were used by rpm to think he is in control of the build process
Created attachment 62518 [details, diff] patch which instructs rpmbuild to clean after himself
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
Reopening for consideration
This is supposed to be fixed in portage-2.2_pre5 or earlier.
