File tree Expand file tree Collapse file tree 2 files changed +5
-5
lines changed Expand file tree Collapse file tree 2 files changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -151,9 +151,9 @@ executable will use the name of the project instead.
151
151
152
152
This is a bit inconsistent, but it's how ` ubi ` has behaved since it was created, and I find this to
153
153
be the sanest behavior. Some projects, for example ` rust-analyzer ` , provide releases as compressed
154
- executables with names like ` rust-analyzer-x86_64-apple-darwin.gz ` and
155
- ` rust-analyzer-x86_64-unknown-linux-musl.gz ` , so installing these as ` rust-analyzer ` seems like
156
- better behavior.
154
+ executables with names like ` rust-analyzer-x86_64-apple-darwin ` and
155
+ ` rust-analyzer-x86_64-unknown-linux-musl ` , so installing these as ` rust-analyzer ` seems like better
156
+ behavior.
157
157
158
158
## How ` ubi ` Finds the Right Release Artifact
159
159
Original file line number Diff line number Diff line change 37
37
//!
38
38
//! This is a bit inconsistent, but it's how `ubi` has behaved since it was created, and I find this
39
39
//! to be the sanest behavior. Some projects, for example `rust-analyzer`, provide releases as
40
- //! compressed executables with names like `rust-analyzer-x86_64-apple-darwin.gz ` and
41
- //! `rust-analyzer-x86_64-unknown-linux-musl.gz `, so installing these as `rust-analyzer` seems like
40
+ //! executables with names like `rust-analyzer-x86_64-apple-darwin` and
41
+ //! `rust-analyzer-x86_64-unknown-linux-musl`, so installing these as `rust-analyzer` seems like
42
42
//! better behavior.
43
43
//!
44
44
//!
You can’t perform that action at this time.
0 commit comments