Re: [AMBER-Developers] AmberTools Versioning

From: Daniel Roe <>
Date: Wed, 29 Feb 2012 10:59:33 -0500

On Wed, Feb 29, 2012 at 10:22 AM, David A Case <> wrote:
> I guess it's OK, although the script will report the latest
> update number as well.  And since updates are no so easy, I think most people
> will automatically have them all.
> The problem with your scheme is that the "current patched" version of
> AmberTools12 would end up with all kinds of version numbers.  antechamber
> might be at version 12, whereas cpptraj would be at version 12.3, and so on.

I was thinking more along the lines of this being more for developer
use. The current way of handling bugfixes and reporting
the patch level is great. Individual program versioning would just be
a way to keep track of what's going on 'under the hood'. You're right
in that it will result in different programs having different version
numbers, but the way I was thinking about it users would use the
output from ' --patch-level' when reporting bugs while
the program's internal version string would be an additional check to
make sure patches have been properly applied. So if I type 'cpptraj
--version' and get 12.3 I know that the latest bugfix to actually
affect cpptraj was 3.


AMBER-Developers mailing list
Received on Wed Feb 29 2012 - 08:00:01 PST
Custom Search