Bug 133993

- Update to 0.81. Most of the changes are due to dougb@ (thanks!), I just upped to .81 which
  contains a IPv6 compatibility fix that caused problems in .80.

Of particular note for committer:

- The patch removes the @dirrm for the DOCSDIR. With it in place, removal fails because it tries
  to remove it twice. portlint -C does complain about the @dirrm being m issing, but if I re-add it
  pkg_delete:s are broken due to repeated removal attempts. Some ports seem to get away with this
  (such as security/wipe) without portlint complaining, but I don't get what the rule is and why it
  complains in my case but not in the wipe case.

Generated with FreeBSD Port Tools 0.77

Upstream ChangeLog:

Version 0.81 (Released: 20090412)

    Network:
     * Fixed IPv6 resolver on FreeBSD (and others?)
     * Increased network buffer-size to 32kb (old: 8kb on Linux, 1kb on FreeBSD)
       This should fix speed issues on *BSD

    BitTorrent:
     * Bugfix: Fixed broken 'tracker show' output (broke in 0.80 due to IPv6)

    Kademlia:
     * IPv6 Support (Experimental: Bitflu is currently the only implementation
                     that supports IPv6-Kad)

    StorageVFS:
     * New configuration option vfs_use_allocator
       Turns bitflus internal pre-allocator on or off
       Setting this to 1 causes bitflu to pre-allocate data.
       This results in more disc activity but can help to avoid fragmentation
       on some filesystems. Setting this to 0 turns the pre-allocation off
       The default is '0' (= Disabled).
       (Note: Bitflu <= 0.80 had this on and you couldn't turn it off)


Version 0.80 (Released: 20090209)

This might be the worst or the best bitflu release ever: You decide (and i
don't care :-p )

Bitflu 0.80 brings you (almost) full IPv6 support. yeah!


     Core:
      * Support for binding an OUTGOING connection to a specific (non-standard)
        Interface has been dropped.
      * Network: IPv6 support!
      * Network: API-Change: Use of IPv4 has been replaced by RemoteIp
      * Config: Bitflu will now create a backup of your configuration file
                while starting up

     StorageVFS:
      * Bugfix: _WriteFile failed to check the return code of print() and close(), this
        could have caused a corrupted clipboard file if you ran out of diskspace


     BitTorrent:
      * Bugfix: analyze_torrent and verify would cause a panic if the specified
                queue_id string did not exist. Oops.
      * Outgoing connections are (again) established less aggressive.
        Bitflu ~0.62 tried very hard to create outgoing connections but
        this would only reward people who are unable to receive
        incoming connections.
      * Tracker: Support IPv6 responses (TCP and UDP!)
      * PEX: Bitflu cann receive IPv6 Peers and will use them .. maybe :-)
      * New command: seedprio: Tells bitflu to reserve X upload slots
                     for a specific torrent
      * New command: seedhide: Tells bitflu to hide X % while seeding a
                     torrent. So bitflu will look like a normal
                     downloader and leechers won't be able to get the
                     full torrent from just a single peer.