-
Notifications
You must be signed in to change notification settings - Fork 0
Think about packaging #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think listing in distros is much more long term.. got to find out if it is useful and people want it first.. |
Just because it is in the same area as the CI builds - and again thinking in the short term about not putting it into public registries. But I believe that we can add "taps" to our Brew (basically point it at github.com/umccr somehow?) and there is some config magic that would allow us to install it on our own macs? Can you investigate what that needs? Possibly needs a special UMCCR brew repo? |
The "canonical" way to publish Rust binaries and libraries (crates) is via https://crates.io ... sure, we can Building packages for distros is quite a "level-up" for when a package becomes mainstream... and requires a significant effort to put it through (and maintain it) via the different channels/builders for Debian/Ubuntu/Fedora, etc... |
Yes understand distros is way down the track - and we would need to demonstrate adoption and usefulness. And crates is the correct way once we have worked out stuff - like what the binary should be called. Though - why would there be an expectation that people who want to use a rust binary are into Rust? i.e. they may not even know what |
Yup yup, very valid points, I'll take this as a template once we retake this, I think it's fairly well written and recent: |
Were this to become a popular/useful utility - how does it get published/available in distros? Brew etc?
I presume we can start with a brew tap immediately and host it via the repo?
The text was updated successfully, but these errors were encountered: