On Thursday, April 30, 2020 at 8:57:45 AM UTC-4, Jay McCarthy wrote: > > If you do so, and if your users need to pin themselves to particular > versions there are broadly two techniques. First, you can create your > own package catalog. Most users typically use two catalogs: the "big" > one on pkgs.racket-lang.org and another "small" one for your > particular release, where the core racket packages are pinned to > particular versions. When we were designing the package system, we > imagined that organizations would maintain their own catalogs of > audited versions of packages so they would not be surprised by any > automatic updates. Second, you can change your package source to pin > to a particular git revision/tag. This might be particularly useful if > a package relies on erroneous behavior of some package that was > otherwise fixed. >
I posted a message in Slack about this also, but in case the mailing list is preferred for whoever has the info, I'll post here also. I'm curious about this approach. The scenario that's important to me is being able to control the versions of packages that my app uses. If a package is updated, and introduces a bug, I don't want that to cause failures in my production app i.e. I want the same set of packages (at specific versions) that I'm developing and testing with on my laptop to be identical to the ones I will eventually install on my servers at a later point in time. Are people using this approach, described by Jay, of hosting their own catalogs, to accomplish this? If so, how do you get setup? In other words, how do you populate the catalog with the specific versions of packages you want? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/ff40b36c-e868-4844-b147-03d2b796f596o%40googlegroups.com.
