This one time, at band camp, Nick Boyce said: > While I understand the problem with the unrar code itself, it seems to > me that simply enabling the --unrar parameter of clamscan should not > entail incorporating or distributing any unrar code at all - the code to > parse the --unrar parameter and call the non-free unrar binary if > specified surely belongs to ClamAV alone ? > > In which case the ClamAV binaries could remain free and distributable > under Debian policy, while individual sysadmins could make their own > decision about whether to install the non-free unrar binary package, and > use the --unrar switch to request that clamscan call it.
Yes, it's a simple bug that prevents it from running the external unpacker right now, nothing to do with software freedom issues. I'm talking to upstream about it, and I'll put a note here when I have something useful to say. -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
