Thanks Dave,
For those of you using a bash script to compile Amber 10 and AmberTools,
something like this should help:
if [[ ! $(grep "THERE ARE NO BUGFIXES" $SOURCEDIR/bugfix.at.all-1.2) ]];
then
patch -p0 -N -r patch-rejects.at < $SOURCEDIR/bugfix.at.all-1.2
else
echo "AmberTools does not need patching, skipping the patch process!"
fi
-----Original Message-----
From: owner-amber.scripps.edu [mailto:owner-amber.scripps.edu] On Behalf
Of David A. Case
Sent: Thursday, July 24, 2008 18:38
To: amber.scripps.edu
Subject: Re: AMBER: Running patch "bugfix.at.all" with AmberTools 1.2
On Thu, Jul 24, 2008, Mike Hanby wrote:
>
> I use a scripted approach to building Amber10 (with AmberTools). With
> AmberTools 1.2 released I downloaded it and ran my build script, it
> fails during the patching process now.
> Any suggestions other than "just don't patch"?
nope. There are updates in version 1.2 that were not deemed crucial
enough
to post as bugfixes. I'll rename the patch file to indicate that it is
intended for AmberTools1.0.
...dac
-----------------------------------------------------------------------
The AMBER Mail Reflector
To post, send mail to amber.scripps.edu
To unsubscribe, send "unsubscribe amber" (in the *body* of the email)
to majordomo.scripps.edu
-----------------------------------------------------------------------
The AMBER Mail Reflector
To post, send mail to amber.scripps.edu
To unsubscribe, send "unsubscribe amber" (in the *body* of the email)
to majordomo.scripps.edu
Received on Sun Jul 27 2008 - 06:07:53 PDT
