-
Notifications
You must be signed in to change notification settings - Fork 38
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
Distribute through Package Managers #10
Comments
That sounds like a good idea! What existing solutions do you have in mind? As Passerine uses GitHub Actions for builds/tests, do you know of any actions can build and distribute standalone binaries across package managers upon release? Thanks! |
@slightknack rust-action looks perfect for this! |
Great, I'll look into it! |
This is a base GitHub Action that builds a number of binaries and adds them to a draft release. I'm not sure if it's correct, which is why I'm putting it in as a PR for review.
* Create release.yml, addresses #10 This is a base GitHub Action that builds a number of binaries and adds them to a draft release. I'm not sure if it's correct, which is why I'm putting it in as a PR for review. * fixed syntax and naming errors * removed stray whitespace, pushing again * potentially fix 'uses or run' error * doing a rather silly manual binary search for the error * failed, so commenting out more * failed, so commenting out even *more* * failed, swapped order of remaining keys * failed again, commenting out all but one key. this should work * that worked. added name to previous step * Uncommented everything but the name keys. this might work * failed, commented out everything but checkout * that worked. uncommenting toolchain * uncommented matrix * think that worked, uncommented mostly everything * failed, moved location of buld matrix * worked, uncommenting cross compile * worked, uncommenting move * worked, uncommented create release * failed, reversed order of id and uses * failed, but I think I fixed everything
I'm working on release.yml (#28) again, and I think I have something that should work. I'm worried about merging it into master now because of what happened last time. |
We're one step closer - there was an issue with passerine/aspen (see rust-build/rust-build.action#2) - but now that that has been (hopefully) resolved, binaries should be built. We'll test it out with the next release. After that's done, all that's left is |
We'll test out this action on the next release, which should be soon. @siraben has also been working on packaging |
FYI, passerine is in nixpkgs. NixOS/nixpkgs#119054 |
@siraben Great! Thanks for your work on this! I'll resolve the tag-version conflict in the next release. |
Here are the package managers I think are a good subset to start. If you're familiar w/ packaging on these systems or would like to contribute packages for another one, please let me know.
|
A quickstart script is fantastic, but I find that having one single source for all packages is even better—you can build out your own CI package or use an existing solution @slightknack
The text was updated successfully, but these errors were encountered: