to compare with the third tarball, so I have no idea what kind of change. I
have asked in the forum[1] and the developer has replied. He said that he does
not remember what kind of change in there, but he promise me that it's safe.
Since nobody knew, so I am going to bump the PORTREVISION in case.
The developer said that he will post in the news next time if he reroll the
tarball to give us the headup the reason of reroll. I think it's fair enough.
[1] http://forum.deluge-torrent.org/viewtopic.php?f=8&t=309
Reported by: krismail
included by accident. Also, they tweaked a bit in setup.py that doesn't affect
anything in runtime as no function change.
-SIZE (deluge-0.5.4.1.tar.gz) = 15536378
+SIZE (deluge-0.5.4.1.tar.gz) = 1480071
Reported by: krismail
libtorrent/src/storage.cpp doesn't know about how to check filesystem on
FreeBSD yet, so instead always use sparse file without check on which
filesystems that have sparse file support. Both UFS and UFS2 have sparse file
support. Bump the PORTREVISION.
The website said, 'There was a licensing problem with the Deluge 0.5.1 tarball
that was released yesterday. This release add no features or bugfixes, but
contains a fixed license. This new release is version 0.5.1.1.' More info
about license fixes visit at http://dev.deluge-torrent.org/changeset/576 ...
to bring a native, full-featured client to Linux, BSD, and other *NIX GTK
desktop environments such as Gnome and XFCE.
Deluge uses Rasterbar's version of libtorrent as the main ingredient in its
bittorrent protocol backend.
WWW: http://deluge-torrent.org/
--
deluge-0.4.90.3 as in Deluge 0.5 Beta 3, I have added two patches from its SVN
to fix the memory leaks.
