[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#580686: ITP: iroffer-dinoex -- IRC file distribution bot


this is my fist package, please comment so I don't send a RFS for nothing if 
the package is wrong.



The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/i/iroffer-dinoex
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/i/iroffer-dinoex/iroffer-

On Friday 07 May 2010 20:50:59 Firas Kraiem wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Firas Kraiem <firas@fkraiem.org>
> Owner: Firas Kraiem <firas@fkraiem.org>
> * Package name    : iroffer-dinoex
>   Version         : 3.21
>   Upstream Author : David Johnson (PMG) <pmg@iroffer.org>
>                     Dirk Meyer (dinoex) <dinoex@dinoex.net>
> * URL             : http://iroffer.dinoex.net/
> * License         : GPLv2
>   Programming Lang: C
>   Description     : IRC file distribution bot
>  iroffer is a fileserver for IRC (commonly referred to as a DCC bot).
>  It uses the DCC feature of IRC to send files to other users. iroffer
>  will connect to an IRC server and let people request files from it.
>  Unlike similar programs, iroffer is not a script; it is a standalone
>  executable written entirely in C, from scratch, with high transfer
>  speed and efficiency in mind. iroffer has been known to reach
>  6MByte/sec or higher bandwidth usage when multiple transfers are
>  occurring at the same time.
>  .
>  iroffer-dinoex is a fork of iroffer developed and maintained by
>  Dirk Meyer. It offers a lot of enhancements and new features,
>  and is backwards-compatible with the original iroffer. New features
>  offered by iroffer-dinoex include support for IPv6, SSL (either via
>  OpenSSL or GNU TLS), passive DCC, large (> 4 GB) files, UPnP, and
>  the ability to extend it via a Ruby scripting engine.

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: