libtorrent is a C++ library that aims to be a good alternative to all the
other bittorrent implementations around. It is a library and not a full
featured client, although it comes with a working example client.
The main goals of libtorrent are to be cpu efficient, memory efficient and
very easy to use.
The 0.16 branch adds uTP support.
Note that this is NOT the same library as the libtorrent port!
WWW: http://www.rasterbar.com/products/libtorrent/
net-p2p/libtorrent-rasterbar
- Update to 0.16.12
- Rename from net-p2p/libtorrent-rasterbar-16 to net-p2p/libtorrent-rasterbar
- Remove conflict with deprecated Port
- Add pkg-message
- Support STAGEDIR
net-p2p/libtorrent-rasterbar-python
- Rename from net-p2p/libtorrent-rasterbar-python-16 to
net-p2p/libtorrent-rasterbar-python
- Change comment and MASTERDIR
- Change dependency to net-p2p/libtorrent-rasterbar
- Add SLAVE_PORT=yes
Approved by: wg (mentor)
Revert r310507 by putting pkg-plist back. The problem is that w/o pkg-plist
file installation of this ports hangs on "Generating temporary packing list"
stage. I discovered that while testing of libtorrent-rasterbar-16-python update
on a live system (while build is fine in tinderbox tests). I found exactly the
same report at [1] while googling of the problem.
Sorry about that.
[1] http://forums.freebsd.org/showthread.php?t=37177
Pointyhat to: rm (myself)
Upgrade to 0.16.4:
* raise the default torrents allowed to announce to trackers to 1600
* improve uTP slow start behavior
* update use of boost.system to not use deprecated functions
* fix GIL issue in python bindings. Deprecated extension support in python
* fixed bug where setting upload slots to -1 would not mean infinite
* extend the UDP tracker protocol to include the request string from the
tracker URL
Add the 0.16 branch of libtorrent-rasterbar
The most revolutionary aspect of the new branch is that it brings in
support for uTP.
This port also brings in a patch consisting of the changes from 0.16.0
release through local SVN revision 6850. These fixes include patches we
had in the 0.15 version of the port, as well as various other fixes that
were reported by me, and others post the 0.16.0 release. These fixes
should be in the 0.16.1 release.