> Jeremy Fairbrass wrote: > > Nigel Horne wrote: > >> The version *is* ClamAV devel-20061213, i.e. it was built from CVS > >> not the release code. That is because the release code does not > >> support Windows. > > > > I had thought that your build was somehow based on the release code, > > just converted over to Windows, like the other Windows > ports (ClamWin > > etc) which do use the 0.88.7 versioning format. > ... > > if the release code doesn't support Windows, then how do those other > > Windows ports do it? > > I don't know the specific facts in this case, but I can give you some > general information that might help clarify things. > > One of the differences you are observing are the efforts > external to the > core ClamAV development team to port ClamAV to windows versus the > internal efforts. The external developers, like the ClamWin project, > start with a released version of the code, and then apply > patches until > it works with Windows. Apparently they retain the original release > numbers when they republish their modified versions. > > In contrast the internal developers (specifically Nigel Horne) are > working to modify the official source code so it supports > Windows. This > work, like typical new development work, is being applied to > the latest > version of the source code, and thus it doesn't have a > release number yet.
I've run both the SOSDG and ClamWin products of ClamAV in the past as well. ClamWin specifically states the released version number in their product, so I would assume they start with the released version code and build from that. SOSDG probably does that as well. I recall notes on their web site about "this version is based on...", but their version number shows similar to the the product at w32.clamav.net-- the development tree version. All three products have strengths and weeknesses. It is my feeling that if ClamAV ever decides to have a supported windows binary release, that it'll probably be closest to what we see at w32.clamav.net and hopefully will display the released version. My guess is that if that happens, SOSDG may decide to abandon their project because it so closely resembles this one. ClamWin OTOH provides significant add-on functionality (a nice GUI) that isn't available in ClamAV itself, so I expect that project will continue. For my current projects, I need a good solid command-line scanner for Windows, which is exactly what I get here. I hope it gets official release and support status in the future, but as long as it's available and working well, I'm likely to continue using it. Thanks for the good work, Nigel. Bret _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
