-
Notifications
You must be signed in to change notification settings - Fork 136
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
move metadata away from workspace manifests #1193
move metadata away from workspace manifests #1193
Conversation
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
hmm I'm not sure we want to have empty files to just to suppress warnings, that feels like the opposite direction see #1194 |
@plebhash, I’m unsure about removing the metadata from the root Cargo file. Another possible way to retain the metadata is by adding it to each crate within the workspace, but that seems excessive. I’m fine with either approach. |
I didn't notice you were assigned to #1192 feel free to modify this PR instead of #1194 but yeah, we can "transfer" the relevant fields from the workspace the main point is that those fields need to be removed from the workspace and we should not suppress the warnings by creating empty packages, that definitely feels like the wrong direction |
883eadb
to
0cbc1dd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few nits:
- What do you think about adding
description
as well? documentation
is always linking to "https://github.com/stratum-mining/stratum", why not link to the specific crate docs on docs.rs?
description = "API for bridging SV1 miners to SV2 pools" | ||
license = "MIT OR Apache-2.0" | ||
documentation = "https://github.com/stratum-mining/stratum" | ||
license = "MIT + Apache-2.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is or, not and
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't get it, Can you elaborate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You changed the license wording from MIT <OR> Apache
to MIT <AND> Apache
, it should stay as OR (i.e., don't change OR to +)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it used +
everywhere except this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
umm not really.. take a look into the files please. it is currently either MIT
or MIT OR Apache
and all of the changes modified it to MIT + Apache
. Anyway, saying MIT AND Apache
is confusing as AND implies both licenses forced together, while its either this or that, however the user wants.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, MIT + Apache
means users can choose either the MIT or Apache 2.0 license. It doesn’t mean both licenses apply together, just that the user has the option to pick one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do think it is confusing to use and
but mean or
.. but anyway this is not a big deal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
turns out this is actually a big deal 😛
|
e59c789
to
34cd893
Compare
I think all of our crates have a page on docs.rs. I would link to that, regardless if the docs are up to date or not. If no docs.rs page for a crate then yea, keeping as is seems reasonable. For the desc, a one liner would be great. Will make the cargo.toml more complete. |
Yup, followed the same. You can check, all the documentation are now pointing to their corresponding crate doc |
34cd893
to
5a7ecea
Compare
@Shourya742 looks like we got a conflict after merging #1198 |
Let me resolve locally... and push.. |
5a7ecea
to
ce2f085
Compare
closes #1192