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. > Although I don't claim to know exactly what CVS means (I kinda have
> an idea)...
CVS is just the tool used to store the source code. It provide an easy
way to retrieve specific versions (releases) of the code, as well as
helping to coordinate changes being made by multiple developers.
You'll often hear the metaphor of a tree applied to the way the code is
stored in a version control system like CVS. The trunk refers to the
main version of the code that evolves over time. Branches are used to
contain specific changes that need to be temporarily or permanently
isolated from the main trunk. So for example, a risky new feature may be
experimented with on a branch, and later when proven stable, merged into
the trunk. > ...is there any way to know which release code version of
> ClamAV corresponds to the code you're using? Eg. is it possible to
> say that the code used for devel-20061213 is the same as that used
> for 0.88.7 or something?
While you can't say it is exactly equivalent to something, there are
usually some assertions you can make. If the Windows modifications are
being applied to the trunk of the code, then the development releases
supporting Windows should closely resemble the highest numbered release
(whether that is an alpha, beta, or final release).
Practically speaking, 0.90 appears to be the current stable release (and
I don't see an alpha or beta release listed on the site), so I'd expect
the development releases to closely resemble it.
Venture Logic, Newton, MA, USA
"Enterprise solutions through open source."
Professional Profile: http://tmetro.venturelogic.com/