I'm using Racket v8.16 on macOS Sequoia. I'm getting back to hacking scribble after 9 months. I had installed a local git clone of scribble in v8.14. I updated to v8.16 by simply installing the distribution. Of course this overlaid my local version of scribble. I'd prefer not to create a new git clone of scribble and then merge my changes into it. I would prefer to just keep using my existing Git repo. I've already merged the latest commits on the master branch into it.
Yeah, it was a typo. I fixed it, it was v8.14. I ended up cloning it, then push the old repo to GitHub, then adding the GitHub repo as a remote, and pulling my code from there.
Next time I update Racket I'll try out the raco pkg migrate command, instead of the little script I use to install my preferred set of packages.
Thanks. However, my hope was that I could avoid cloning a rather large git repo, since I already had it on my filesystem. But it's good to know I could have just jammed it in place, instead of pushing and pulling my changes through a shared git repo.
There is way to do this (as done by various GHA workflows in the Racket repos -- DrRacket, Typed Racket, and others all do this), and there are even lower-level Raco commands to do this. But I don't know enough Raco to adapt the commands and fill in the details.