On Fri, Jun 19, 2020 at 01:09:08PM -0700, Brian Adkins wrote: > > I'm hoping the main scenario I'm concerned about (a bug is introduced in an > update of a package) is rare, although that's exactly what motivated Alex > to create his system. If it is a rare scenario for me, then I'd like to do > the following: > > 1) Develop & test locally while updating packages as needed > 2) Prior to releasing to production, so *something* that effectively > snapshots my environment > 3) Use the snapshot to deploy to production > > Although I have some ideas about the "something" task, I still have to > finalize the procedure and try it out. One option is to simply use a > racksnap snapshot. What I'd like to do is to create a personal catalog that > represents the packages I currently have installed, but it doesn't appear > there's a super easy `raco pkg` command to do that - I still need to > research a bit. Either there is a command, or it seems like a relatively > straightforward thing to add.
Making a complete copy of everything stored under ~/.racket might make enough of a racket system snapshot on a GNU/Linux system. I have no idea what to do on Windows, though. -- hendrik -- 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/20200619204945.rj6kckxwmsvutag6%40topoi.pooq.com.
