You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We used to always put our binaries directly in the root of our .tar.gz archives. distseems to be hard coded to always add a subdir for the non zip files. We're trying to completely move to cargo-dist but we need to keep our already released tools working. As we have a self-update cli command that requires this setup.
Hey! What you have right now looks great. You can submit a PR and I'll make a follow-up PR myself adding a test or two and documentation.
It may take us a little bit to merge it, because I want to investigate how it interacts with dist's updater feature (so I can make sure they play nice together), but it's definitely functionality we want and your code is a very good starting point. 🙂
Hey team! Thanks for the great tool!
We used to always put our binaries directly in the root of our
.tar.gz
archives.dist
seems to be hard coded to always add a subdir for the nonzip
files. We're trying to completely move tocargo-dist
but we need to keep our already released tools working. As we have aself-update
cli command that requires this setup.I already made a fork and implemented a first version for myself to test it in our workflow: main...ruben-arts:cargo-dist:feature/allow_binaries_in_root_of_tar
Let me know if you would be open to a contribution of this sort.
The text was updated successfully, but these errors were encountered: