On 16/2/2011, at 4:27 p.m., Jason Swails wrote:
> This is why I put in an "if [ -x /bin/ln ]; then" add the link (otherwise
> just copy).
Ah, that makes more sense!
> If that's the case, though, Amber makes such extensive use of
> links already (netcdf, the bin, include, lib dirs in AmberTools, etc.) that
> this should hardly be the straw that breaks the camel's back.
True enough.
> Along these lines, I have a branch in which I've implemented the
> one-config.h-idea (AmberTools/src/config.h) and it works. Any reason I
> should refrain from pushing this to the master and seeing how it goes?
>
> As a side-note, one nice thing about having a symlink (or hard link) is that
> config.h can be edited in either source directory (obviously not the case
> with the one-config.h approach).
>
> Thoughts?
I'd say forge ahead!
--
For greater security, I support S/MIME encryption.
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
- application/pkcs7-signature attachment: smime.p7s
Received on Wed Feb 16 2011 - 16:00:04 PST
