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

Crates.io page shows no readme info #6

Closed
bvibber opened this issue Aug 15, 2019 · 5 comments
Closed

Crates.io page shows no readme info #6

bvibber opened this issue Aug 15, 2019 · 5 comments

Comments

@bvibber
Copy link
Owner

bvibber commented Aug 15, 2019

https://crates.io/crates/mtpng doesnt show the readme as i expect from other projects

Not sure what have to do to fix that

@bvibber
Copy link
Owner Author

bvibber commented Aug 15, 2019

Fixed it, had to specify 'readme' entry pointing to readme.md

@bvibber bvibber closed this as completed Aug 15, 2019
@waldyrious
Copy link

@Brion shouldn't that be the default behavior? Maybe this could be reported as a suggestion to the Crates project. I found this issue that seems to be suggesting the same thing, but the response is not clear to me.

@bvibber
Copy link
Owner Author

bvibber commented Aug 15, 2019

@waldyrious I expected it to act like Github and autodetect my common-named file, but having to specify it is not a big deal as long as it's documented. https://doc.rust-lang.org/cargo/reference/manifest.html doesn't seem to mention it except in an example listing, where it's explained well enough but I didn't find it on my first pass through the docs.

@waldyrious
Copy link

I expected it to act like Github and autodetect my common-named file

I think that's a reasonable expectation, and see no reason why it shouldn't be the case.

I didn't find it on my first pass through the docs.

So, even if it is undesirable for some reason to have the automatic README detection, better documentation seems clearly needed.

I would make either suggestion myself but I didn't understand the closing reasoning in the issue I linked above. Does it make sense to you? What are they saying would be the proper channel to report/request that?

@bvibber
Copy link
Owner Author

bvibber commented Aug 16, 2019

My understanding of the note there is that the field should be auto-filled by Cargo before it gets sent to crates.io, so they recommend opening an issue directly on Cargo's tracker: https://github.com/rust-lang/cargo/issues

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

2 participants