Comments (5)
There was a bit of a discussion on Reddit on this topic when we first made the project public, which I still stand by:
I’m split on whether that’s a good idea, because no one would use pipes-rs as a library, and you can just as easily use the
cargo install --git
command posted by u/charlatanoftime above me. Crate names are very limited; I’d like to avoid contributing to that.
Sorry, I didn’t make myself clear. I do know about publishing binary-only crates, but I personally think that it’s a waste of crate names when you can almost as easily use
cargo install --git
. I just realised that, even if I wanted to, publishing pipes-rs would require publishing all its subcrates. At that point versioning of these subcrates has to be introduced, so I think it’s all more trouble than it’s worth.
If you’d like a convenient way to install from source, then you can use
$ cargo install --git https://github.com/lhvy/pipes-rs
In the end it’s down to @lhvy though because it’s his project.
from pipes-rs.
I agree with @arzg’s point, and I’d prefer to stick to just cargo install --git
. It would be nice though if the install link in the readme could be for a specific/latest version, as opposed to the latest commit.
from pipes-rs.
Not planned on fixing for reasons listed above, opened a new issue regarding improving the current install instructions.
from pipes-rs.
Hmmm, it would be trivial to come up with a little one-liner that curl
s the latest release, untars, and then runs cargo install --path pipes-rs-v1.6.0/
or something.
from pipes-rs.
Ah yeah, that's understandable! Didn't think about checking on reddit, so I appreciate the clarification 😄
from pipes-rs.
Related Issues (20)
- rainbow mode! HOT 3
- Migrate to clap v4
- Compensate for character dimensions
- Thread Crash/Panic HOT 6
- Replace cargo install instructions with command to cargo install latest version HOT 1
- Build universal binaries for macOS
- Using config file: `Error: failed to read config` HOT 3
- Readme typo HOT 3
- Switch to alternate allocator
- Build failed, Compiling nanorand v0.5.2, error[E0277]: arrays only have std trait implementations for lengths 0..=32 HOT 1
- List available keys in the readme
- Performance issues with large numbers of pipes HOT 2
- Should we limit the FPS? HOT 1
- Fails to install HOT 3
- Typo in readme HOT 1
- Set `codegen_units` to 1 for release builds HOT 1
- Set `panic = "abort"` for release builds HOT 1
- Add benchmarks HOT 1
- Use newly-stabilised `std::ops::ControlFlow` HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pipes-rs.