Explain how to control whether Planet auto-installation is enabled
This commit is contained in:
parent
680b6f4928
commit
1741e1b0d1
|
@ -8,6 +8,7 @@
|
|||
planet/util
|
||||
planet/version
|
||||
planet/syntax
|
||||
planet/resolver
|
||||
planet/scribble)
|
||||
scribble/bnf)
|
||||
|
||||
|
@ -160,6 +161,15 @@ Once that is complete, PLaneT will use that version of the
|
|||
package for any subsequent @racket[require]s and won't try
|
||||
to use the network.
|
||||
|
||||
If you wish to ensure that PLaneT won't use the network even if your
|
||||
operating system allows it, you can use the @racket[download?]
|
||||
parameter of the @racketmodname[planet/resolver] module to control
|
||||
whether it attempts to download files. Similarly, you can use the
|
||||
@racket[install?] parameter to prevent installation. Finally, you can
|
||||
block access at the operating system level to the path returned by
|
||||
@racket[(PLANET-BASE-DIR)] to control which operating system users can
|
||||
install PLaneT packages.
|
||||
|
||||
@subsection{Fine-Grained Control Over Package Imports}
|
||||
|
||||
The PLaneT client is designed to balance two competing goals:
|
||||
|
|
Loading…
Reference in New Issue
Block a user