> > Package catalogs do not generally store any code, merely references to > other people's code. There's no way they can guarantee that old > tar-balls are still around. You can easily lock yourself in to a > specific version by using the `raco pkg catalog-copy/catalog-archive` > commands and distributing/saving the resulting catalog. >
They don't have to guarantee tar balls of the package at arbitrary points in time are around. They *do* have to guarantee that they have some understanding of multiple sources for a single package name, each with a different version. Locking yourself to a built package is a lot different than locking yourself to any package a catalog claims has the correct name and version. There is a pressing need for this, and it'll get much more pressing as the number of package users increases. -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/602e7e20-c0ef-4c8b-94e4-4c08e826781c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
