Re: [clamav-users] Windows packaging

2012-06-25 Thread Paul Whelan
On 25 Jun 2012 at 9:55, Tom Judge wrote: > Hi Paul, > > On 24/06/2012 18:15, Paul Whelan wrote: > > What's the reason for the change in the packaging of the windows > > binaries? > > > > The windows binaries where packaged with custom shell script before, > now they are packaged by VisualStudi

Re: [clamav-users] Windows packaging

2012-06-25 Thread Steve Basford
> VisualStudio does not have a target to build a ZIP file, we could also > build a cab file if this would help. > Hi Tom, Any use? http://markkemper1.blogspot.co.uk/2010/10/zipping-build-outputs-using-build-file.html http://stackoverflow.com/questions/4794503/is-there-a-zip-project-in-visual-st

Re: [clamav-users] Windows packaging

2012-06-25 Thread Török Edwin
On 06/25/2012 05:26 PM, Tom Judge wrote: > On 25/06/2012 10:10, aCaB wrote: >> FYI unrar license is incompatible with the GPL. That was the >> rationale in the packaging. > > > Yes that is why they are separate binaries. As far as we can tell > there is nothing that states that you can't put th

Re: [clamav-users] Windows packaging

2012-06-25 Thread Tom Judge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/06/2012 10:10, aCaB wrote: > On 06/25/12 15:55, Tom Judge wrote: >>> Exclusion of the necessary msvc* runtime libraries >> >> The inclusion of them helps lower the barrier to entry for >> people to try ClamAV on windows. > > So why have you rem

Re: [clamav-users] Windows packaging

2012-06-25 Thread aCaB
On 06/25/12 15:55, Tom Judge wrote: >> Exclusion of the necessary msvc* runtime libraries > > The inclusion of them helps lower the barrier to entry for people to > try ClamAV on windows. So why have you removed them? >> Inclusion of the previously separate libclamunrar libs > > There is no rea

Re: [clamav-users] Windows packaging

2012-06-25 Thread Tom Judge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/06/2012 04:34, Steve Basford wrote: > >> On Mon, Jun 25, 2012 at 08:13:58AM +0100, Steve Basford wrote: >>> While I can see the MSI installer being useful to some >>> people... I'd prefer to have the .ZIPs back (or have both >>> built), as I've

Re: [clamav-users] Windows packaging

2012-06-25 Thread Tom Judge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Paul, On 24/06/2012 18:15, Paul Whelan wrote: > What's the reason for the change in the packaging of the windows > binaries? > The windows binaries where packaged with custom shell script before, now they are packaged by VisualStudio when we bui

Re: [clamav-users] Windows packaging

2012-06-25 Thread Steve Basford
> On Mon, Jun 25, 2012 at 08:13:58AM +0100, Steve Basford wrote: >> While I can see the MSI installer being useful to some people... I'd >> prefer to have the .ZIPs back (or have both built), as I've got to run >> the >> MSI >> installer, find where the files have been installed and them copy them

Re: [clamav-users] Windows packaging

2012-06-25 Thread Henrik K
On Mon, Jun 25, 2012 at 08:13:58AM +0100, Steve Basford wrote: > While I can see the MSI installer being useful to some people... I'd > prefer to have the .ZIPs back (or have both built), as I've got to run the > MSI > installer, find where the files have been installed and them copy them out, > so

Re: [clamav-users] Windows packaging

2012-06-25 Thread Steve Basford
> Your best bet is to ask on the ClamWin forum. Here is the forum site > http://forums.clamwin.com/ I'm not sure if he's talking about the binaries here, auto-built by ClamAV Team (not the version by the ClamWin team) http://sourceforge.net/projects/clamav/files/clamav/win32/ The builds used to

Re: [clamav-users] Windows packaging

2012-06-24 Thread Jim Preston
On 06/24/2012 03:15 PM, Paul Whelan wrote: What's the reason for the change in the packaging of the windows binaries? The differences include: Creation of a msi install in place of the previously zipped executables and libraries Exclusion of the necessary msvc* runtime libraries Inclusion of

[clamav-users] Windows packaging

2012-06-24 Thread Paul Whelan
What's the reason for the change in the packaging of the windows binaries? The differences include: Creation of a msi install in place of the previously zipped executables and libraries Exclusion of the necessary msvc* runtime libraries Inclusion of the previously separate libclamunrar libs