Menu
Where would a raco pkg install --auto drracket install the drracket package by default? This is off of a preexisting homebrew installation of racket.
689
In general, each argument to raco pkg install is a package source. A package source can refer to a ".zip" file, a ".tar" file, a Git repository, a directory-structured web site, or a few other possibilities. In each of those cases, a package name is inferred from the package source.
Use raco pkg install in the ‹pkg-name› directory: If you use raco pkg show at this point, you’ll see a line for ‹pkg-name›. The “Source” column will show that it’s a linked package, and the “Checksum” column will say #f , which means that there is no checksum.
raco pkg remove ‹option› ... ‹pkg› ... — Attempts to remove the given packages. By default, if a package is the dependency of another package that is not listed, this command fails without removing any of the ‹pkg› s. If a package scope is not specified, the scope is inferred from the given ‹pkg› s.
Users installing the package from Racket 6.0 will use the default source for the package, while those using Racket 5.3.5 will install from the alternative branch, tag, or archive. For more details, see Package Catalog Protocol.
Try the following to print where your Racket install is installing packages:
Welcome to Racket v6.4.0.11.
-> (require setup/dirs)
-> (find-pkgs-dir)
#<path:/racket/share/pkgs>
-> (find-user-pkgs-dir)
#<path:/racket/add-on/development/pkgs>
(those paths are made up for this example so you will want to actually run this on your machine)
The first path is for installation scope packages, e.g., the packages that come with Racket. The second path is for user scope packages.
If you want to find where a particular package is installed, you can use this package: raco-find-collection
138
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
