suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Adding documentation notes re Eli

Browse Source
This commit is contained in:
Jay McCarthy 2013-04-08 06:40:49 -06:00
parent ccda5a84ad
commit c396d1e435
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
collects/pkg/scribblings/pkg.scrbl
View File

@ -387,7 +387,7 @@ View and modify package configuration options. It accepts the following @nonterm
} }
@item{@command/toc{create} @nonterm{option} ... @nonterm{package-directory} @item{@command/toc{create} @nonterm{option} ... @nonterm{package-directory}
--- Bundles a package. It accepts the following @nonterm{option}s: --- Bundles a package directory into a package archive. It accepts the following @nonterm{option}s:
@itemlist[ @itemlist[
@item{@DFlag{format} @nonterm{format} --- Specifies the archive format. @item{@DFlag{format} @nonterm{format} --- Specifies the archive format.
@ -482,9 +482,16 @@ package source when they use @exec{raco pkg update}.
@subsection[#:tag "manual-deploy"]{Manual Deployment} @subsection[#:tag "manual-deploy"]{Manual Deployment}
@margin-note{By default, @exec{raco pkg create} generates a Zip
archive. For more options, refer to the @command-ref{create}
documentation. If you want to generate an archive through some other
means, simply archive what you made in the first part of this
section. For more formal details, refer to the @tech{package}
definition.}
Alternatively, you can deploy your package by publishing it on a URL Alternatively, you can deploy your package by publishing it on a URL
you control. If you do this, it is preferable to create an archive you control. If you do this, it is preferable to create an archive
first: from your package directory first:
@commandline{raco pkg create @nonterm{package}} @commandline{raco pkg create @nonterm{package}}