py-kenosis-bittorrent contains a kenosis enabled version of bittorrent thus making it a distributed application. The tracker is no longer limitted to a single location but rather the tracking information is distributed along the kenosis network. Therefore, avoiding single points of failure. This is just a proof of concept on what can be done with kenosis This application is based on the official BitTorrent client version 3.4.2 (namely port net/py-bittorrent) and; thus, shares the port code base, patches and installation procedures. Therefore, I would like the following repo copy to maintain this information. ports/net/py-bittorrent -> ports/net/py-kenosis-bittorrent One question though, it installs the same files as py-bittorrent; however, it's not exactly a drop in replacement since it works the same way but it's kenosis related. Should I install the script files in the same location as py-bittorrent (thus, adding a CONFLICTS line) or in a non-standard location (PREFIX/libexec/kenosis-bittorrent/)?
State Changed From-To: open->repocopy Repocopy request
Responsible Changed From-To: freebsd-ports-bugs->portmgr Portmgr's territory
State Changed From-To: repocopy->open Repo-copy completed.
Responsible Changed From-To: portmgr->lioux Repo-copy completed.
State Changed From-To: open->closed Post repo copy updates finished.