Automated method for making racket package installs consistent?

[primer]

If I have an an install with packages X and Y installed, and a second install with packages Y and Z installed, is there a way to use raco.exe or some such to get X, Y, and Z installed on both machines without having to figure out "by hand" which packages are missing from each install?

[William J. Bowman]

I'm not sure what you're asking: is your question equivalent to figuring out which packages are explicitly installed?

> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/da026119-c6c8-470f-b125-c6982b2b558fn%40googlegroups.com.

[Robert Postill]

Hi Primer,

Have you tried raco pkg migrate?  I have used this before and it's pretty painless from my POV.  The docs are at https://docs.racket-lang.org/pkg/cmdline.html#%28part._raco-pkg-migrate%29.

Hope that helps.

Robert

[primer]

On Sunday, October 11, 2020 at 1:35:24 AM UTC-7 William J. Bowman wrote:

I'm not sure what you're asking: is your question equivalent to figuring out which packages are explicitly installed?

That's part of the problem.  I have several computers, each with racket installed.  I'd like to get them on the same page in terms of the explicitly installed packages, which are currently different on each machine depending on what I played with at the time.

So I imagine the workflow to be something like this:

1.  On machine A, do something that generates a list of explicitly installed packages

2.  Do something on machine B to bring in that list of packages and automatically install them, while not disturbing any explicit packages already installed on B

3. Repeat steps 1 and 2 starting with the now updated B.  After this A and B should be in sync.

[schle...@gmail.com]

This is just a suggestion, that does not help with your current dilemma, a strategy how you could prevent it in the future:

Create or expand your personal dotfile repository, within that repository create a folder my-racket-packages, within that folder create a info.rkt:

#lang info
(define collection "my-racket-packages")
(define deps
  (list "lens"
        "opengl"
        "gregor"
        "add your own packages here"))

This way you can create a personal package that lists all of the packages that you play around with explicitly.

https://docs.racket-lang.org/pkg/metadata.html
You can then just use drracket or raco to install that package locally.

Within the directory:

raco pkg install

to install the package.
When the dotfiles have changed, within the my-racket-packages directory:

raco pkg update --auto

I know this solution requires you to update the package manually, but if you install a package via raco pkg install <package-name>, you might as well add it to the info.rkt instead.

This way you have a single source of truth, instead of having to sync multiple different installations.

Instead of my-racket-packages you also could name it my-racket-experiments and save your experiment sessions with scripts along with the dependencies.
You never have to publish that package if you don't want to.

[Sam Tobin-Hochstadt]

The list of explicitly-installed packages is available from `raco pkg
show`. You could use a script to parse that, or you can use
`installed-pkg-table` from `pkg/lib` to get the list in Racket.

Sam

> --
> 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...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/6cbeacf9-cebe-4c1a-9d49-9fe75d2eb39dn%40googlegroups.com.