Is raco setup --check-pkg-deps <my-collection> broken? When I run it on a small project with a few direct deps (no dynamic require) where the info.rkt says only (define deps '("base")) (define build-deps '("at-exp-lib" "rackunit-lib" "scribble-lib" "racket-doc")) it doesn’t report anything, whereas one of the file has several requires (details in thread)

(require racket/dict racket/list racket/pretty racket/string racket/format racket/port racket/random (for-syntax racket/base syntax/parse) define2 global) where define2 and global are third-party deps

Dependency checking works by looking at compiled files, so if you’re skipping compilation of that module with compile-omit-files, the dependency won’t be detected.

I do use compile-omit-files, but not on the file that has these dependencies. Is that the expected behaviour anyway?

No, and now I see that https://github.com/Metaxal/wordle-solver omits different files. But when I install that (after define2 and global), I do get a complaint from raco setup --check-pkg-deps wordle-solver, so I don’t know what else would be going wrong.

hm, something must be messed up in my configuration or installation I guess

When I add dependencies manually I get this error from raco setup --check-pkg-deps : pkg: no such directory path: /home/laurent/.local/share/racket/other-version/pkgs/../../../Prog/Racket/define2/

Not sure why the path is relative, since raco pkg show shows an absolute path, and also there should be 5 "../", not 3

Why are some link installed as relative and others as absolute, when both are installed with raco pkg install --link? ("define2" "/home/laurent/Prog/Racket/define2") ... ("wordle-solver" (up up up up #"abc" #"def" #"Prog" #"Racket" #"wordle-solver"))) (taken from links.rktd)

There’s a links.rktd~ from March 2021 where the paths are all relative strings and look very different from links.rktd. Could it be related?

I’m not sure this is relevant, but is “other-version” a regular directory, or is it a soft link?

regular