Hi all,
I've opened a PR (#2532) that adds maiko, notecards, loops, and test
as git submodules of the medley repository. Here's what this means for
day-to-day development.
WHY
The build scripts (loadup-apps-from-full.sh, medley.command, etc.)
already looked for these repos inside $MEDLEYDIR first, before falling
back to sibling directories. Formalizing them as submodules means:
- The medley repo records exactly which commit of each sub-repo was
used for a given build, making builds reproducible.
- Contributors no longer need to manually clone each repo in the right place.
- CI workflows can replace multiple separate checkout steps with a
single submodule init.
WHAT CHANGED
- .gitmodules added with entries for maiko (master), notecards (main),
loops (main), and test (master)., online (main)- maiko/ removed from
medley .gitignore so it can be tracked as a submodule.
- No changes to any build scripts -- the paths are the same as before.
might need to look at do_hcfiles.sh script
WHAT YOU NEED TO DO
If you have an existing clone of medley:
git pull
git submodule update --init --recursive
This will populate the maiko/, notecards/, loops/, online/ and test/
directories inside your medley checkout. If you already have those
repos cloned as siblings (../maiko, ../notecards, etc.), you can keep
using them -- the build scripts still fall back to those paths.
For a fresh clone:
git clone --recurse-submodules
https://github.com/Interlisp/medley
To update submodules to the latest upstream commits in the future:
git submodule update --remote
The PR is at
https://github.com/Interlisp/medley/pull/2532. will wait
for feedback.
Thanks,
Larry