Bug#164842: my ITP of dcc -- Distributed Checksum Clearinghouse
Hi guys! I don't seem to have enough free time to finish packaging dcc. If anyone is interested in taking over the ITP, please contact me. Be warned though, that this is not very easy to package: the build process is non-standard, the package installs files all over the place, it requires some patching to be able to run as an ordinary user, and from the docs it's not really clear what each binary exactly does, nor which config files it wants read or write access to. This is not a my first package package. It would probably be best if the person to take this, has (unlike me) used dcc before. There are some halfway done packages available at http://people.debian.org/~bas/dcc/. Oh, a reminder of what DCC is: The Distributed Checksum Clearinghouse or DCC is a cooperative, distributed system intended to detect bulk mail or mail sent to many people. It allows individuals receiving a single mail message to determine that many other people have been sent essentially identical copies of the message and so reject the message. Upstream is Vernon Schryver [EMAIL PROTECTED] (haven't contacted him yet); there seems to be a lot of active devlopment going on. Homepage is http://www.rhyolite.com/anti-spam/dcc/. Licence is BSD without advertising clause. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED], [EMAIL PROTECTED] | bon le faire?| | GPG key: 0644fab7 | Pablo Picasso | +---+
Bug#164842: my ITP of dcc -- Distributed Checksum Clearinghouse
On Sat, Feb 01, 2003 at 06:03:20PM +0100, Bas Zoetekouw wrote: Hi guys! I don't seem to have enough free time to finish packaging dcc. If anyone is interested in taking over the ITP, please contact me. That's too bad. :-( I don't have time to work on it in the forseeable future, either. Be warned though, that this is not very easy to package: the build process is non-standard, the package installs files all over the place, it requires some patching to be able to run as an ordinary user, and from the docs it's not really clear what each binary exactly does, nor which config files it wants read or write access to. This is not a my first package package. It would probably be best if the person to take this, has (unlike me) used dcc before. That's why I didn't try to take it in the first place. Have you contacted upstream for help? Generally in this sort of a situation, upstream is glad to help; the more users, the better it works. Thanks, -- Duncan Findlay
