|
165 | 165 | //!
|
166 | 166 | //! ## Special considerations
|
167 | 167 | //!
|
168 |
| -//! Registry dependencies do not track the mtime of files. This is because |
169 |
| -//! registry dependencies are not expected to change (if a new version is |
170 |
| -//! used, the Package ID will change, causing a rebuild). Cargo currently |
171 |
| -//! partially works with Docker caching. When a Docker image is built, it has |
172 |
| -//! normal mtime information. However, when a step is cached, the nanosecond |
173 |
| -//! portions of all files is zeroed out. Currently this works, but care must |
174 |
| -//! be taken for situations like these. |
| 168 | +//! Cargo currently partially works with Docker caching. When a Docker image is |
| 169 | +//! built, it has normal mtime information. However, when a step is cached, the |
| 170 | +//! nanosecond portions of all files is zeroed out. Currently this works, but |
| 171 | +//! care must be taken for situations like these. |
175 | 172 | //!
|
176 | 173 | //! HFS on macOS only supports 1 second timestamps. This causes a significant
|
177 | 174 | //! number of problems, particularly with Cargo's testsuite which does rapid
|
@@ -1108,13 +1105,8 @@ fn calculate_normal<'a, 'cfg>(
|
1108 | 1105 | })
|
1109 | 1106 | }
|
1110 | 1107 |
|
1111 |
| -// We want to use the mtime for files if we're a path source, but if we're a |
1112 |
| -// git/registry source, then the mtime of files may fluctuate, but they won't |
1113 |
| -// change so long as the source itself remains constant (which is the |
1114 |
| -// responsibility of the source) |
1115 | 1108 | fn use_dep_info(unit: &Unit<'_>) -> bool {
|
1116 |
| - let path = unit.pkg.summary().source_id().is_path(); |
1117 |
| - !unit.mode.is_doc() && path |
| 1109 | + !unit.mode.is_doc() |
1118 | 1110 | }
|
1119 | 1111 |
|
1120 | 1112 | /// Calculate a fingerprint for an "execute a build script" unit. This is an
|
|
0 commit comments