On Fri, Mar 16, 2012, Tyler Luchko wrote:
>
> Will the next version of the release be taken from the Git repo or has
> the released version already forked?
>From git. Release candidates are created by running the mkrelease and
mkrelease_at scripts from the master branch at git.ambermd.org.
> I think we should have a consistent policy as to what happens when some
> functionality is not available with a particular compiler or whatever.
> IMO, I think configure should _always_ die with an error message and
> explicit instructions on how to proceed. My previous error message
> would return the user's original configure command modified such that
> RISM would not be built by adding '-norism' and removing any instances
> of '-rism'. This way they could copy and paste to quickly get to the
> next step but also knew exactly what functionality was missing.
Sounds good. The main thing that often doesn't get built is xleap, and it
should not be hard to change how configure handles that case to conform with
the suggestion above. We could certainly also require that -norism be added
to the command line -- as you point out, that helps the user understand what
is going on.
....dac
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Mar 16 2012 - 19:30:03 PDT
