Skip to content
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

Update Rust Crate #1919

Closed
bkmgit opened this issue Jul 13, 2022 · 6 comments
Closed

Update Rust Crate #1919

bkmgit opened this issue Jul 13, 2022 · 6 comments

Comments

@bkmgit
Copy link

bkmgit commented Jul 13, 2022

Bug Report

The Rust crate available at https://crates.io/crates/zola/0.1.1 is outdated

Environment

Zola version: 0.1.1

Expected Behavior

Update the crate, perhaps using a GitHub action

Current Behavior

Not applicable

Step to reproduce

Not applicable

@Keats
Copy link
Collaborator

Keats commented Jul 13, 2022

I'm not going to upload it to crates.io unless there's a way to group workspace dependencies into a single crate transparently.

@Keats Keats closed this as completed Jul 13, 2022
@bkmgit
Copy link
Author

bkmgit commented Jul 13, 2022

Ok.

@c-git
Copy link
Contributor

c-git commented Jul 13, 2022

@Keats sorry to bother you, could you explain what you mean? I'm curious what is happening and what you think should be happening

@Keats
Copy link
Collaborator

Keats commented Jul 13, 2022

Zola is divided in sub crates (https://github.com/getzola/zola/tree/master/components) to make it easier to test/faster to compile. To publish to crates.io atm, I would need to publish all those irrelevant crates that are inter-dependent and have no use outside of Zola. There has been some proposals to consider those internal crates as implementation details and allow pushing a single crate to crates.io but not implemented so far.

@c-git
Copy link
Contributor

c-git commented Jul 13, 2022

Thank you for taking the time to explain (Interestingly enough this morning I was reading about workspaces in rust)

@damccull
Copy link

I know this is old, but is it possible to set up the single zola crate such that its dependencies are pointing at git repos, and therefore only need to publish the one zola crate? I guess that'd probably make it more difficult to maintain though, so maybe not worth it.

Zola is divided in sub crates (https://github.com/getzola/zola/tree/master/components) to make it easier to test/faster to compile. To publish to crates.io atm, I would need to publish all those irrelevant crates that are inter-dependent and have no use outside of Zola. There has been some proposals to consider those internal crates as implementation details and allow pushing a single crate to crates.io but not implemented so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants