On Fri, Apr 09, 2004 at 02:04:55AM +0200, Martin Helas may have written: > > * Package name : dcc > Version : 1.2.39 > Upstream Author : "Vernon Schryver" <[EMAIL PROTECTED]> > * URL : http://www.rhyolite.com/anti-spam/dcc/ > * License : BSD without advertising clause > Description : Distributed Checksum Clearinghouse for emails
While I am not completely familiar with all of Debian's policies regarding packaging, I am familiar with the DCC. It would seem to me that based on the way Debian tends to do things, as well as the fact that the upstream author himself releases separate tarballs based on the functionality required, that you should be releasing separate packages for different programs. For example, you could have packages named dcc-dccproc, dcc-dccm, dcc-dccifd, dcc-dccd, and perhaps a dcc-common. Not all sites will need dccd, and those of us who do not use sendmail will not want to have sendmail milter libraries installed just to have a packaged version of DCC. The bare minimum for a client-only install would be dccproc and the common package containing cdcc and related tools. Cheers, -- Brian T Glenn delink.net Internet Services
pgp00000.pgp
Description: PGP signature
