Comment 5 for bug 332711

Your updated ebuild nearly worked, though I had to rename it to remote-help-assistant-access-0.1.4.ebuild and also re-tar the tar.gz so that it extracted to the remote-help-assistant-access-0.1.4 directory instead of remote-help-assistant-access-0.1.4~bug332711r1 (and of course the automatic download of the remote-help-assistant-access-0.1.4.tar.gz did not work because it is not there yet). I guess the ~bug332711r1 appendix is just some launchpad artifact.

Updated ebuilds could have a -r1, -r2, -r3 attached (like remote-help-assistant-access-0.1.4-r1.ebuild), but more complicated file and directory names make things more complicated (you'd have to stick a line with S="${WORKDIR}/unpacked-directory-name" into the ebuild at least).

The copyright and changelog were also copied to the correct directory.

The "setup.py install" also worked, and I found in another ebuild that we could use "python setup.py install --root="${D}" || die" to copy everything to the sandbox install directory (and let setup.py do what it's supposed to do; I'm not sure what that is, though). I still got a /usr/lib/python2.5/site-packages/remote_help_assistant_access-0.1.4_bug332711r1-py2.5.egg-info, so some part of my renaming didn't quite work, it seems.

Yes, the openssh package on Gentoo always has client and server.