ports/76200: REPOCOPY net/py-bittorrent to net/py-kenosis-bittorrent

[Mario Sergio Fujikawa Ferreira]

>Number:         76200
>Category:       ports
>Synopsis:       REPOCOPY net/py-bittorrent to net/py-kenosis-bittorrent
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 13 14:00:39 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Mario Sergio Fujikawa Ferreira
>Release:        FreeBSD 5.3-STABLE i386
>Organization:
>Environment:
System: FreeBSD exxodus.here.here 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Dec 28 13:38:16 BRST 2004 lioux at exxodus:/usr/obj/usr/src/sys/LIOUX i386

>Description:

	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/)?

>How-To-Repeat:
>Fix:



>Release-Note:
>Audit-Trail:
>Unformatted: