How does a Racket user prevent Racket tools they run from accessing the
default package server catalogs, by default? And also make Racket use
their own package catalogs, by default?
Probably I'm just not finding one piece of documentation that already
exists?
I see the following encouraging bit in the docs
("https://docs.racket-lang.org/pkg/Package_Concepts.html#%28tech._package._catalog%29";):
PLT supports two package catalog servers that are enabled by default:
https://pkgs.racket-lang.org for new packages and
http://planet-compats.racket-lang.org for automatically generated
packages for old PLaneT packages. Anyone may host a package catalog,
and any file-serving HTTP host can act as a basic package catalog
server. See Package Catalog Protocol for information on how package
information is extracted from a catalog.
I assume that a different set of package catalogs can be selected on a
per-user or per-project basis, without modifying the core Racket
installation files themselves, but I can't find documentation of how to
do this.
For example, on a Unix-like system, with Racket installed under
"/usr/local/racket-6.8", I assume there is a way to do this with
environment variable or with a dotfile in the user's home directory.
I see that `raco pkg` has a `--catalog` argument, which could come in
handy for scripting, but that's not sufficient for general use.
Right now, I'm mostly interested in making Racket never, ever even try
to access the default catalog servers.
Later, there is an important use case for making Racket use a user's own
package catalogs by default, such as on a per-organization and/or
per-big-project basis. (Though that's not as important as disabling the
default ones, since we still have the filesystem links.)
--
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.
For more options, visit https://groups.google.com/d/optout.
