-
Notifications
You must be signed in to change notification settings - Fork 177
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
Publish unpublished crates to crates.io #2002
Comments
It looks like it's possibly only the astral-sh UV crates that aren't on cargo. Stuff like that: distribution-filename = { git = "https://github.com/astral-sh/uv", tag = "0.4.0" }
distribution-types = { git = "https://github.com/astral-sh/uv", tag = "0.4.0" } |
Yep there are quite a few of them. We did split pixi into several crates. Some of them do not depend on any of the astral crates and we do plan on publishing those to crates. Unfortunately for the pixi binary itself we cant until astral decides to publish some of those crates. |
You might be able to fork and publish the forks but yeah that'd be annoying
to maintain.
Have you reached out to astral and asked them to consider publishing
themselves? They might just not think that anyone is using their crates.
…On Sat, Sep 7, 2024, 13:45 Bas Zalmstra ***@***.***> wrote:
Yep there are quite a few of them. We did split pixi into several crates.
Some of them do not depend on any of the astral crates and we do plan on
publishing those to crates.
Unfortunately for the pixi binary itself we cant until astral decides to
publish some of those crates.
—
Reply to this email directly, view it on GitHub
<#2002 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF77AQIBRZUUF4B2SOW7MU3ZVLRM7AVCNFSM6AAAAABNZ562P6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZVGE3DCNRYGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
We sure have but unfortunately no luck. Forking and publishing their work also doesnt seem appropriate. If I may ask, why would you prefer to get pixi from crates.ion? You can still install pixi with cargo by using a git reference. |
I couldn't find a very explicit request in the uv issue list to publish unpublished crates to crates.io Here are some related issues though:
Did I miss something? Reasons for using crates.io for everything instead of relying on git for some: Using Git dependencies in Cargo instead of crates.io introduces several risks:
Plus easier source installs, reusability etc |
He @corneliusroemer, We completely agree, and if there was a way to handle it with a level of maintenance that we found acceptable, we would have done it already. We've had offline conversations with the A short counter-argument for why we’re not too worried about using
The biggest downside right now is that you can't |
Problem description
I noticed that in the "install from source" guide you mention that one can't cargo install pixi from crates.io because of reliance on unpublished crates.
It might be nice to publish those unpublished crates to crates.io
Are these crates you developed or dependencies? Which ones are they?
The text was updated successfully, but these errors were encountered: