Add some pieces of an IPC framework that will eventually allow ebuild
authorZac Medico <zmedico@gentoo.org>
Thu, 12 Aug 2010 17:01:02 +0000 (10:01 -0700)
committerZac Medico <zmedico@gentoo.org>
Thu, 12 Aug 2010 17:01:02 +0000 (10:01 -0700)
commit1d42bc5eadc68c5b9ab2d50334c9e54cae0c4d84
treee9d392cb18e4ad366da144048f8b1ccadd2ca44f
parent5161a86d03fb95af601b3f9722f936346d9f7ae1
Add some pieces of an IPC framework that will eventually allow ebuild
processes can to communicate with portage's main python process.

Here are a few possible uses:

1) Robust subshell/subprocess die support. This allows the ebuild
   environment to reliably die without having to rely on signal IPC.

2) Delegation of portageq calls to the main python process, eliminating
   performance and userpriv permission issues.

3) Reliable ebuild termination in cases when the ebuild has accidentally
   left orphan processes running in the backgraound (as in bug 278895).
bin/ebuild-ipc [new file with mode: 0755]
bin/ebuild-ipc.py [new file with mode: 0755]
pym/_emerge/FifoIpcDaemon.py [new file with mode: 0644]
pym/portage/tests/ebuild/test_ipc_daemon.py [new file with mode: 0644]