File tree 4 files changed +28
-12
lines changed 4 files changed +28
-12
lines changed Original file line number Diff line number Diff line change 31
31
executable binary or example target. {{man "cargo-install" 1}} will use the
32
32
packaged lock file if the ` --locked ` flag is used.
33
33
- A ` .cargo_vcs_info.json ` file is included that contains information
34
- about the current VCS checkout hash if available (not included with
35
- ` --allow- dirty` ) .
34
+ about the current VCS checkout hash if available, and whether or not the
35
+ worktree is dirty.
36
36
3 . Extract the ` .crate ` file and build it to verify it can build.
37
37
- This will rebuild your package from scratch to ensure that it can be
38
38
built from a pristine state. The ` --no-verify ` flag can be used to skip
@@ -52,12 +52,16 @@ Will generate a `.cargo_vcs_info.json` in the following format
52
52
``` javascript
53
53
{
54
54
" git" : {
55
- " sha1" : " aac20b6e7e543e6dd4118b246c77225e3a3a1302"
55
+ " sha1" : " aac20b6e7e543e6dd4118b246c77225e3a3a1302" ,
56
+ " dirty" : true
56
57
},
57
58
" path_in_vcs" : " "
58
59
}
59
60
```
60
61
62
+ ` dirty ` indicates whether or not the Git worktree was dirty when the package
63
+ was built.
64
+
61
65
` path_in_vcs ` will be set to a repo-relative path for packages
62
66
in subdirectories of the version control repository.
63
67
Original file line number Diff line number Diff line change @@ -29,8 +29,8 @@ DESCRIPTION
29
29
packaged lock file if the --locked flag is used.
30
30
31
31
o A .cargo_vcs_info.json file is included that contains information
32
- about the current VCS checkout hash if available (not included
33
- with --allow- dirty) .
32
+ about the current VCS checkout hash if available, and whether or
33
+ not the worktree is dirty.
34
34
35
35
3. Extract the .crate file and build it to verify it can build.
36
36
o This will rebuild your package from scratch to ensure that it can
@@ -51,11 +51,15 @@ DESCRIPTION
51
51
52
52
{
53
53
"git": {
54
- "sha1": "aac20b6e7e543e6dd4118b246c77225e3a3a1302"
54
+ "sha1": "aac20b6e7e543e6dd4118b246c77225e3a3a1302",
55
+ "dirty": true
55
56
},
56
57
"path_in_vcs": ""
57
58
}
58
59
60
+ dirty indicates whether or not the Git worktree was dirty when the
61
+ package was built.
62
+
59
63
path_in_vcs will be set to a repo-relative path for packages in
60
64
subdirectories of the version control repository.
61
65
Original file line number Diff line number Diff line change 26
26
executable binary or example target. [ cargo-install(1)] ( cargo-install.html ) will use the
27
27
packaged lock file if the ` --locked ` flag is used.
28
28
- A ` .cargo_vcs_info.json ` file is included that contains information
29
- about the current VCS checkout hash if available (not included with
30
- ` --allow- dirty` ) .
29
+ about the current VCS checkout hash if available, and whether or not the
30
+ worktree is dirty.
31
31
3 . Extract the ` .crate ` file and build it to verify it can build.
32
32
- This will rebuild your package from scratch to ensure that it can be
33
33
built from a pristine state. The ` --no-verify ` flag can be used to skip
@@ -47,12 +47,16 @@ Will generate a `.cargo_vcs_info.json` in the following format
47
47
``` javascript
48
48
{
49
49
" git" : {
50
- " sha1" : " aac20b6e7e543e6dd4118b246c77225e3a3a1302"
50
+ " sha1" : " aac20b6e7e543e6dd4118b246c77225e3a3a1302" ,
51
+ " dirty" : true
51
52
},
52
53
" path_in_vcs" : " "
53
54
}
54
55
```
55
56
57
+ ` dirty ` indicates whether or not the Git worktree was dirty when the package
58
+ was built.
59
+
56
60
` path_in_vcs ` will be set to a repo-relative path for packages
57
61
in subdirectories of the version control repository.
58
62
Original file line number Diff line number Diff line change @@ -43,8 +43,8 @@ packaged lock file if the \fB\-\-locked\fR flag is used.
43
43
.sp
44
44
.RS 4
45
45
\h '-04' \(bu \h '+02' A \fB \& .cargo_vcs_info.json \fR file is included that contains information
46
- about the current VCS checkout hash if available (not included with
47
- \fB \-\- allow \- dirty \fR ) .
46
+ about the current VCS checkout hash if available, and whether or not the
47
+ worktree is dirty.
48
48
.RE
49
49
.RE
50
50
.sp
@@ -74,13 +74,17 @@ Will generate a \fB\&.cargo_vcs_info.json\fR in the following format
74
74
.nf
75
75
{
76
76
"git": {
77
- "sha1": "aac20b6e7e543e6dd4118b246c77225e3a3a1302"
77
+ "sha1": "aac20b6e7e543e6dd4118b246c77225e3a3a1302",
78
+ "dirty": true
78
79
},
79
80
"path_in_vcs": ""
80
81
}
81
82
.fi
82
83
.RE
83
84
.sp
85
+ \fB dirty \fR indicates whether or not the Git worktree was dirty when the package
86
+ was built.
87
+ .sp
84
88
\fB path_in_vcs \fR will be set to a repo\- relative path for packages
85
89
in subdirectories of the version control repository.
86
90
.sp
You can’t perform that action at this time.
0 commit comments