3
3
### Is the plan to use GitHub as a package repository?
4
4
5
5
No. The plan for Cargo is to use [ crates.io] , like npm or Rubygems do with
6
- npmjs.org and rubygems.org.
6
+ [ npmjs.com ] [ 1 ] and [ rubygems.org] [ 3 ] .
7
7
8
8
We plan to support git repositories as a source of packages forever,
9
9
because they can be used for early development and temporary patches,
@@ -23,8 +23,9 @@ central registry model as well as a Git-based model, and most packages
23
23
are downloaded through the registry in those ecosystems, with an
24
24
important minority of packages making use of git-based packages.
25
25
26
- [ 1 ] : https://www.npmjs.org
26
+ [ 1 ] : https://www.npmjs.com
27
27
[ 2 ] : https://bundler.io
28
+ [ 3 ] : https://rubygems.org
28
29
29
30
Some of the advantages that make a central registry popular in other
30
31
languages include:
@@ -135,9 +136,9 @@ picture to decide what versions of dependencies should be used.
135
136
with wildcard dependency constraints.**
136
137
137
138
While libraries _ can_ , strictly speaking, they should not. A version requirement
138
- of ` * ` says “This will work with every version ever,” which is never going
139
+ of ` * ` says “This will work with every version ever”, which is never going
139
140
to be true. Libraries should always specify the range that they do work with,
140
- even if it’s something as general as “every 1.x.y version.”
141
+ even if it’s something as general as “every 1.x.y version”.
141
142
142
143
### Why ` Cargo.toml ` ?
143
144
0 commit comments