You might also be interested in the new `raco-pkg-env` tool: https://github.com/samdphillips/raco-pkg-env/
Sam On Tue, May 18, 2021 at 12:20 PM Matthew Flatt <[email protected]> wrote: > > Yes, this approach can work. I don't think the existing Racket tools > will help much with persisting a configuration across versions, though, > so you'd probably have to script that. > > One potential drawback of your approach is that executables, > documentation, etc., associated with the extra package will get > rendered into the main installation area instead of the "/opt/Racket" > are. That may be fine for your purposes, but a more strictly layered > installation is meant to be possible. It turns out that some pieces > have been missing for layering, and fixing that is an area of current > work (https://github.com/racket/racket/commit/dfbb7040a). > > At Sun, 16 May 2021 23:43:52 -0500, Nathaniel W Griswold wrote: > > Hello, > > > > I was setting up Racket on my linux box and i realized that there are a lot > > of > > options for path configuration and i forgot a lot of what i discovered last > > time i dug into this. I was trying to set up installation scope but maybe a > > little cleanly and figured someone might have some input. > > > > I want a package at roughly installation scope, but i kinda wanted to know > > what > > was added by me and what was part of the default installation. Is this > > reasonable or should i just deal with it and dump stuff in > > $RACKET/share/pkgs? > > If it is reasonable then what is the best way to set this up? > > > > Just FYI I did an in-place install of Racket in "/opt/Racket/Racket\ 8.1" > > symlinked to /opt/Racket... > > > > I think maybe what i want is to set to something like > > > > (in /opt/Racket/etc/config.rktd) > > > > #hash(... (pkgs-search-dirs . "/opt/Racket 8.1/share/pkgs-system" #f) > > (links-search-files . ("/opt/Racket/share/pkgs-system/links.rktd" #f)) ...) > > > > Then i just did a `sudo /opt/Racket/bin/raco pkg install --scope-dir > > /opt/Racket/share/pkgs-system rash` > > > > ... and the new package seems to be working fine for my users. > > > > Is that what i wanted or is there something better? Is there a way to > > configure > > config.rktd additions that will persist across upgrades or will i have to > > update my config.rktd for every racket release? Do other people do this > > kind of > > thing or just dump stuff in the installation scope? Maybe there are more > > options with a unix-style install, i haven't really tried one yet. > > > > Thanks! > > > > Nate > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-users/20210518102000.1b1%40sirmail.smtps.cs.utah.edu. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAK%3DHD%2Ba2G41L5C3v1wPjackfsn0VwtRZEWO7XiW9POS7mWa85Q%40mail.gmail.com.
