AFAIK, proxy65 is the lone implementation of JEP 65 (http://www.jabber.org/jeps/jep-0065.html), which specifies a mechanism for file-transfer and other bytestreams between jabber clients even in cases where both clients are behind NATs. I have created an ebuild for this package. Please let me know if I need to change anything to get this in the tree. I think it's a halfway-decent first stab, though. Note: I have to use the CVS version because the released versions don't work with recent versions of Twisted. Note 2: no dependency on jabber server is intentional - nothing says the proxy has to be on the same machine as the server. Thanks...files follow. Mike Nerone
Created attachment 67870 [details] CVS-based proxy65 ebuild
Created attachment 67871 [details] proxy65 initscript for FILESDIR
I tried making an ebuild a couple of months ago for this but i droped the idea. I'll see what you have done.
Any comments on my ebuild? Has anyone else tried it?
Just a note that current CVS doesn't work with that ebuild anymore. Probably a new dependency or something. Error when trying to generate a tap or start the service is "No module named protocols.jabber". I'm gonna take a look at it.
Created attachment 77843 [details] Updated proxy65-cvs ebuild Turns out protocols.jabber is not included in base Twisted anymore - it's been broken out into Twisted Words. Here's a new ebuild with dependencies modified to reflect this change. Note: Twisted Words is not marked stable yet, nor are some if its dependencies, so you'll have to put something akin to the following in /etc/portage/package.keywords: <dev-python/twisted-words-0.2 <dev-python/twisted-web-0.6 <dev-python/twisted-2.1 <dev-python/twisted-xish-0.2 Mike Nerone
BTW, I don't use this anymore (as openfire has the functionality built-in). WONTFIX would be alright with me.
for the unmasking off the twisted-words try using the tool autounmask, simply run the command: emerge autounmask to install, and then run the command: autounmask catagory/package-version hope this helps
BTW, project is now at http://code.google.com/p/proxy65/ . As I said, I personally don't care about this anymore.
*** Bug 296002 has been marked as a duplicate of this bug. ***