The activate_then script had been checking out a specific version of -site
and -core on its first run and warning users if they were out of date. Git
provides much of this functionality already with git submodules, so use them
instead. Submodules also simplify updates, bringing the user to later versions
if there isn't a conflict.
This only affects the -site and -core checkouts as the -parser's docker image
doesn't include the git submodule info.
This should resolve #482, and should probably go in before #483. Users may need to
rm -rf eregs_libs
to see these updates going forward (and git won't clobber existing checkouts).
cmc333333
commented
6 years ago
The
activate_thenscript had been checking out a specific version of -site and -core on its first run and warning users if they were out of date. Git provides much of this functionality already with git submodules, so use them instead. Submodules also simplify updates, bringing the user to later versions if there isn't a conflict.This only affects the -site and -core checkouts as the -parser's docker image doesn't include the git submodule info.
This should resolve #482, and should probably go in before #483. Users may need to
to see these updates going forward (and git won't clobber existing checkouts).