On Mon, Jul 2, 2012 at 8:38 AM, David A Case <case.biomaps.rutgers.edu>wrote:
> On Fri, Jun 29, 2012, Jason Swails wrote:
> >
> > Another idea is to package up and release a AmberTools 12.11 which has
> all
> > 11 patches applied and logged...
> >
> > This has the side-benefit of no divergence between different AT downloads
> > (i.e., everyone has the same thing still, whether by using patch_amber.py
> > the whole time or downloading the new tarball).
>
> But wouldn't the same thing be true if the modified tarball just had the
> updated configure script? I guess I'd rather that everyone have (almost)
> the
> same files from the tarball, than to have to start dealing with users that
> have different starting points.
>
My argument was simply that if we release a tarball with a modified
configure, then people would have two different configure scripts depending
on when they downloaded AmberTools. If we release a 12.11 (or 12.12), then
anyone whose "./patch_amber.py --patch-level" returns the same results will
have *exactly* the same files barring custom changes.
Admittedly the difference in the top-level configure b/w the two downloads
won't cause/prevent any errors that users see, but we are restricted from
patching it if different people have different versions. Is this a severe
restriction? Unlikely, but I'm not sure...
Thanks!
Jason
--
Jason M. Swails
Quantum Theory Project,
University of Florida
Ph.D. Candidate
352-392-4032
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Mon Jul 02 2012 - 06:00:04 PDT
