Some ebuilds and eclasses use EBUILD_DEATH_HOOKS already. I think that feature should be covered in an EAPI and an official, function-based interface shall be developed for it. Use cases: - listing additional files to attach to bugs, - killing leftover processes.
src_death()?
(In reply to comment #1) > src_death()? Maybe. Not sure if it's the most friendly solution since the latter use is more of a enable/disable kind.
Additional files should be pkg_info. For killing leftover processes, I'm strongly inclined to say that ebuilds shouldn't be doing that, and that if we're after some kind of ebuild-induced parallelism support, the package mangler should be doing it.
(In reply to comment #3) > Additional files should be pkg_info. Doesn't that imply that pkg_info() has to be aware of ${T} out of the build sequence? > For killing leftover processes, I'm strongly inclined to say that ebuilds > shouldn't be doing that, and that if we're after some kind of ebuild-induced > parallelism support, the package mangler should be doing it. They're after starting some daemon needed for tests whenever there's no better alternative. For example, dev-python/pymongo needs to start a local instance of mongod for tests. If build is interrupted, the daemon stays alive... By the way, I'm completely fine with something like using cgroups to kill all the children. But that'll work on Linux only. I just thought it would be better to be able to clean up the mess ebuilds may cause.
