recent changes to portage-2.1 moved package|rpm targets to misc-functions.sh and removed them from EBUILD_PHASES list. I was using this through /etc/portage/bashrc to detect in phase I am, and do adequate corrections w/o touching ebuilds (redo false links that point to /var/tmp/portage/*, change absolute links to relative, remove unneeded files and the like. I have tried adding them back to EBUILD_PHASES, but I do not achieve anything. If this was an unintended change, please correct, else please give me a pointer how I get those back to do it locally.
Created attachment 84415 [details, diff] EBUILD_PHASE support for package and rpm This is in svn r3125 for the next release.
On more hunk was needed, in svn r3126. === modified file 'pym/portage.py' --- pym/portage.py +++ pym/portage.py @@ -2246,6 +2246,8 @@ # XXX: that creates a deadlock... Really need to isolate that. mysettings.reset(use_cache=use_cache) mysettings.setcpv(mycpv,use_cache=use_cache) + + mysettings["EBUILD_PHASE"] = mydo if debug: # Otherwise it overrides emerge's settings. # We have no other way to set debug... debug can't be passed in
it is not solved (tested w/ pre7-r5)
sorry for the noise, overseen the next part of patch, now it is ok (at least setup|compile|package work), thanks
Released in 2.1_pre8-r1.
