hi,
I think mkrelease_at is for initial release, where there is no patch at
that time.
Hai
On Thu, Mar 2, 2017 at 1:00 AM, Yong Duan <duan.ucdavis.edu> wrote:
>
> Sorry, spoke too soon ☹.
>
> The patches are there, but the “mkrelease” scripts happily ignored them.
> Need to change the mkrelease scripts slightly and add .patches/{} to
> mkrelease_at.
>
> yong
>
> On 3/1/17, 9:31 PM, "Yong Duan" <duan.ucdavis.edu> wrote:
>
>
> Oh, this is definitely such a mundane thing, but, can some kind
> soul take a look at the patch/update script/configuration ☺. In the present
> amber16-with-patches branch, when one downloads the code and runs
> configure, it checks the patches, which is fine. Then, it downloads the
> patches and thinks those patches already applied still need to be applied.
> Of course, it just quits after realized the patches cannot be applied.
> Perhaps, the “.patch” directory should also be in the branch to keep track
> of the patches already applied?
>
> yong
>
>
>
>
>
>
>
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
>
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Mar 01 2017 - 22:30:03 PST
