Alright, I managed to install from local clone. Thank you Philip! Some observations here. You were right, I should've cloned from my fork. Else `raco pkg update` keeps pulling from the original (Racket central) URL. Docs tell us we can supply alternative URL, and it works but sadly not for multi packages that share the same clone or repo. Yeah, raco docs tell us this too, so no complaints https://docs.racket-lang.org/pkg/git-workflow.html#%28part._clone-link%29
Either way, when raco pkg update pulls updates to the clone, it will still > pull them from the repository corresponding to ‹pkg-name›’s old source, and > not from the git remote ‹url›. Usually, that’s what package developers > want; when they’re not actively modifying a package, other developers’ > updates should be pulled from the package’s main repository. In case where > ‹url› is the preferred source of updates for raco pkg update, use ‹url› in And indeed I confirmed that by running: raco pkg update -j 8 --clone . > https://github.com/vkz/rackunit.git?path=rackunit Which pulls from that fork but only rackunit and not its dependencies that in fact reside in the same repo, for those it keeps going to Racket central. Solution would be to use correct fork for the original clone, but I can't be bothered to go through that again. But IIUC I may as well just stick with git flow for managing my repo, where I control my remotes. Right? raco update doesn't really perform any magic beyond what I'd get by simply git pulling into a linked clone? Thank you for your help Philip and Alex. I have unmitigated fear of package managers. raco has been mostly good to me so far, but omg it is rich ))) -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
