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

pkg manage docs: clairfy in overview that a git repo tag is allowed

Browse Source
This commit is contained in:
Matthew Flatt 2014-10-20 18:05:59 -05:00
parent c15422b577
commit 13f5aa240c
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
pkgs/racket-pkgs/racket-doc/pkg/scribblings/getting-started.scrbl
View File

@ -215,7 +215,7 @@ name} that was resolved by a @tech{package catalog}, then the
@tech{checksum} for the package, and the package is updated if the @tech{checksum} for the package, and the package is updated if the
@tech{checksum} doesn't match the current installation. If the package @tech{checksum} doesn't match the current installation. If the package
was installed directly from a Git reference, then the Git repository is was installed directly from a Git reference, then the Git repository is
consulted to get the current commit of a particular branch, and the consulted to get the current commit of a particular branch or tag, and the
package is updated if the commit identifier doesn't match the package is updated if the commit identifier doesn't match the
@tech{checksum} of the current installation. @tech{checksum} of the current installation.
@ -371,8 +371,9 @@ is:
@inset{@exec{https://github.com/@nonterm{user}/@nonterm{package}.git}} @inset{@exec{https://github.com/@nonterm{user}/@nonterm{package}.git}}
If you want the package to be @nonterm{branch} instead of @exec{master}, If you want the package to be @nonterm{branch} or @nonterm{tag}
then add @filepath{#@nonterm{branch}} to the end of the package source. instead of @exec{master}, then add @filepath{#@nonterm{branch}} or
@filepath{#@nonterm{tag}} to the end of the package source.
Whenever you Whenever you
@ -554,10 +555,10 @@ allow package authors to specify alternative @tech{package source}s to be used
when installing a given package using a specific version of Racket. when installing a given package using a specific version of Racket.
For example, a package that uses on Racket 6.0-specific features could provide For example, a package that uses on Racket 6.0-specific features could provide
a @tech{version exception} for Racket 5.3.6 using a different branch in the a @tech{version exception} for Racket 5.3.6 using a different branch or tag in the
package's GitHub repository, or a different zip archive, as package source. package's GitHub repository, or a different zip archive, as package source.
Users installing the package from Racket 6.0 will use the default source for Users installing the package from Racket 6.0 will use the default source for
the package, while those using Racket 5.3.5 will use the alternative branch / the package, while those using Racket 5.3.5 will install from the alternative
archive. branch, tag, or archive.
For more details, see @secref{catalog-protocol}. For more details, see @secref{catalog-protocol}.