00:33 <Raito_Bezarius> Hi there, I'm trying to provide packaging infrastructure for Racket in NixOS (https://nixos.org) and I would like to understand if I have a right model of how Racket believes where "are" the modules and how to "use" them: currently, I will attempt to build racket, build each modules with this specific racket (version), then build a "wrapped racket with a new config.rtkd with a tree of symlinks to

00:33 <Raito_Bezarius> each compiled modules in a proper folder", then I will attempt to verify that all modules are installed by running Racket code, am I right, that, as a high level plan, this would provide "virtualenv"-like feature for Racket?

00:33 <Raito_Bezarius> For now, I exclude cross-compilation concerns, but I'm interested in how much Racket do depend on external dynamic libraries and how does he handle that (search lib dirs, I assume?)

00:34 <Raito_Bezarius> Racket modules *

01:43 <samth> Raito_Bezarius: you should talk to Philip McGrath, who has done a lot of work packaging Racket for Guix and will likely have useful advice

01:43 <samth> you might also be interested in https://github.com/samdphillips/raco-pkg-env/

01:44 <samth> Racket depends extensively on external dynamic libraries, which it expects to find via the usual search paths for dlopen on Linux

01:47 <Raito_Bezarius> samth: thanks for the pointers!

01:51 <samth> Raito_Bezarius: I would also suggest that IRC is not likely to reach very many other members of the Racket community; I'm the only core developer who uses it.

01:51 <samth> more frequented fora include: Discord, Slack, Discourse

01:52 <samth> and GitHub of course

01:52 <Raito_Bezarius> I see, thank you for the suggestion samth