Ebuild for PyProtocols, a framework for creating adapters/interfaces in Python. This installs PyProtocols, a stable module, as a standalone apart from PEAK (bug #45906), which is alpha. Also, unit testing check is incorporated in ebuild. (ebuild attached below)
Created attachment 34846 [details] PyProtocols-0.9.2.ebuild
Thanks for submission, but before we add this ebuild to portage, you should correct it to use the 'distfiles' eclass.
Created attachment 34851 [details] PyProtocols-0.9.2.ebuild Sorry -- now inherits distutils
Created attachment 34852 [details] PyProtocols-0.9.2.ebuild Arg, take two
Created attachment 34853 [details] PyProtocols-0.9.2.ebuild And take three
Thanks for the ebuild - it's now added to cvs. I moved the tests to src_test() which is supported by the FEATURES="maketest" option in portage-2.0.51*. It's commented for now as it tries to rm files from ${ROOT} and needs a patch..
> It's commented for now as it tries to rm files from ${ROOT} and needs a patch.. Just to clarify for my information, is this a bug inside the PyProtocols tests, or is it a bug with Portage's src_test() handling?
The test function tries to install pyprotocols to the live root filesystem and even tries to rm it afterwards, so it's not really a portage problem.