From jan@swi.psy.uva.nl Thu Mar 22 10:24:04 2001
Received: from gollem.swi.psy.uva.nl (root@gollem [145.18.152.30])
	by swi.psy.uva.nl (8.11.2/8.11.2) with ESMTP id f2M9O3306797;
	Thu, 22 Mar 2001 10:24:03 +0100 (MET)
Received: (from jan@localhost)
	by gollem.swi.psy.uva.nl (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id f2M9O2v20404;
	Thu, 22 Mar 2001 10:24:02 +0100
Date: Thu, 22 Mar 2001 10:24:02 +0100
Message-Id: <200103220924.f2M9O2v20404@gollem.swi.psy.uva.nl>
From: Jan Wielemaker <jan@swi.psy.uva.nl>
Subject: Re: [SWIPL] SWI-Prolog 4.0.2/XPCE 5.1.2
To: Mark Toleman <markt@usq.edu.au>, Jan Wielemaker <jan@swi.psy.uva.nl>
In-Reply-To: Mark Toleman's message of Thu, 22 Mar 2001 12:07:13 +1000 (EST)
Phone: +31 - 20 - 525 6121
Cc: prolog@gollem.swi.psy.uva.nl

Mark,

> Jan, when I download the Full Source to my Windows NT box, the virus
> checker from McAfee tells me the file has a virus (unknown) which
> can't be cleaned.
> 
> Is this likely/possible or is it more likely a problem at my end
> (not something I've had before).

The full source is a .tar.gz file (e.g. date).  The only executable
bits are the makefiles (pl\src\rules.mk and Makefile.mak in many
directories).  Creating the archive is done from a Unix machine that
isn't directly in touch with any Windows machine.  The windows machine
used for development is a Windows-NT/TSE machine using SP6.  Operated
as normal user and the relevant programs are read-only to normal
users.

In theory virusses could work themselves in the makefile and travel
trough the version control-system to the main repository but I believe
this is highly unlikely.

	--- Jan

