~evhan/beaker

9e6f782ad564ac1d6252144615f1e72576981d4f — Evan Hanson 1 year, 8 months ago d87efb5
Minor clarifications to chicken-lock documentation
1 files changed, 7 insertions(+), 7 deletions(-)

M chicken-lock.scm
M chicken-lock.scm => chicken-lock.scm +7 -7
@@ 8,20 8,20 @@
;;;

;;
;; The `chicken-lock` program generates an snapshot of all dependency versions
;; for the given eggs, or any egg files in the current directory.
;; The `chicken-lock` program generates a snapshot of all dependency versions
;; for the given eggs, or for any egg files in the current directory.
;;
;; The output is an override file that can then be used to install those same
;; versions later on using the "-override" or "-from-list" flags. For example,
;; you can record the current version of the r7rs egg and all of its
;; dependencies, and then restore them later, like this:
;; versions later on via the "-override" or "-from-list" flags to `chicken-install`.
;; For example, you can record the current version of the r7rs egg and all of
;; its dependencies, and then restore them later, like this:
;;
;;     $ chicken-lock r7rs > r7rs.lock
;;     ... time passes...
;;     $ chicken-install -override r7rs.lock r7rs
;;
;; If no eggs are given on the command line, this program will look for egg
;; files in the current directory. This can be used to record the current
;; If no egg names are given on the command line, this program will look for
;; egg files in the current directory. This can be used to record the current
;; version of all dependencies for an egg in local development:
;;
;;     $ cat example.egg