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

hints and updates on Git package sources in "Getting Started" docs

Browse Source
This commit is contained in:
Matthew Flatt 2016-03-23 13:39:07 -05:00
parent b1ba506b52
commit 92f4f8ad10
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -385,7 +385,9 @@ is:
If you want the package to be @nonterm{branch} or @nonterm{tag}
instead of @exec{master}, then add @filepath{#@nonterm{branch}} or
@filepath{#@nonterm{tag}} to the end of the package source.
@filepath{#@nonterm{tag}} to the end of the package source. If your
package is a subdirectory @nonterm{path} within the repository, add
@filepath{?path=@nonterm{path}} to the end of the package source.
Whenever you
@ -395,9 +397,10 @@ your changes will automatically be discovered by those who use
@command-ref{update} after installing from your
GitHub-based @tech{package source}.
As of Racket version 6.1.1.1, other Git repository services can work
Other Git repository services@margin-note*{Support for services other
than GitHub requires Racket version 6.1.1.1 or later.} can work
just as well as GitHub---including Gitorious or BitBucket---as long as
the server supports either the ``smart'' HTTP(S) protocol or the
the server supports either the HTTP(S) protocol or the
native Git protocol (but use a @exec{git://} path for the latter).
The Racket package manager provides more support for Git-based