From 1741e1b0d1c7dce6178d3e07e09161627c6c3765 Mon Sep 17 00:00:00 2001 From: Jay McCarthy Date: Wed, 27 Nov 2013 19:22:58 -0700 Subject: [PATCH] Explain how to control whether Planet auto-installation is enabled --- pkgs/planet-pkgs/planet-doc/planet/planet.scrbl | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/pkgs/planet-pkgs/planet-doc/planet/planet.scrbl b/pkgs/planet-pkgs/planet-doc/planet/planet.scrbl index 5e3897d538..f7f04266ac 100644 --- a/pkgs/planet-pkgs/planet-doc/planet/planet.scrbl +++ b/pkgs/planet-pkgs/planet-doc/planet/planet.scrbl @@ -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: