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

cabal check should warn when readme or changelog exist but aren't included in extra-source-files #3964

Closed
sjakobi opened this issue Oct 9, 2016 · 18 comments · Fixed by #8657

Comments

@sjakobi
Copy link
Member

sjakobi commented Oct 9, 2016

Browsing hackage would be a lot nicer if everyone would upload their READMEs.

Would it be within the scope of cabal check to look for a README in the package directory and give a warning/suggestion, if that file isn't listed among the extra-source-files?

If such a warning is not within the scope of cabal check, is there another command that could be reasonably enhanced with such a warning?

@ezyang
Copy link
Contributor

ezyang commented Oct 9, 2016

Seems like a reasonable thing to me.

@23Skidoo
Copy link
Member

23Skidoo commented Oct 9, 2016

While we're at it, we should also add a warning for missing changelog.

@sjakobi sjakobi changed the title Nudge authors to include READMEs in tarballs by adding a warning to cabal check? cabal check should warn when readme or changelog exist but aren't included in extra-source-files Oct 9, 2016
@sjakobi sjakobi self-assigned this Oct 20, 2016
sjakobi added a commit to sjakobi/cabal that referenced this issue Oct 20, 2016
@ezyang ezyang modified the milestones: Triaged, 2.0 Oct 25, 2016
@ezyang
Copy link
Contributor

ezyang commented Oct 25, 2016

@sjakobi Don't forget to PR your change! :)

@sjakobi
Copy link
Member Author

sjakobi commented Oct 26, 2016

I will! :)

I still need to make my patch work with glob patterns in the extra-source-files section, but that won't be much work.

@23Skidoo 23Skidoo modified the milestones: 2.0.1, 2.0 Feb 17, 2017
@23Skidoo 23Skidoo modified the milestones: 2.0.1, 2.0.2 Sep 19, 2017
@23Skidoo 23Skidoo modified the milestones: 2.0.2, 2.4 Aug 29, 2018
@23Skidoo 23Skidoo modified the milestones: 2.4, 2.4.1 Sep 17, 2018
@23Skidoo 23Skidoo modified the milestones: 2.4.1.0, 2.4.2.0 Apr 26, 2019
@phadej phadej modified the milestones: 2.4.2.0, 3.4 Nov 27, 2019
@jneira
Copy link
Member

jneira commented Aug 18, 2021

I think this makes sense @sjakobi do you think your work could be shared as a draft pr? thanks!

@sjakobi
Copy link
Member Author

sjakobi commented Jan 20, 2022

@jneira Apologies for the late response! AFAIK all my work on this issue is in this commit: sjakobi@7dedf0c.

If anyone is interested in completing this work, feel free to use that code in any way you see fit.

@Mikolaj
Copy link
Member

Mikolaj commented Jan 29, 2022

@sjakobi: thank you very much. I've labelled this correctly, so let's hope somebody picks it up now.

@Mikolaj
Copy link
Member

Mikolaj commented Mar 26, 2022

I put these in extra-doc-files. Is that a bad choice?

@Mikolaj
Copy link
Member

Mikolaj commented Mar 26, 2022

I think extra-source-files is actually a bad choice. Should we warn "are you sure your README/changelog is displayed by your executable or otherwise used when compiling your code?"? I guess too many persons make that mistake, so rather not, especially if we are not ready to scan the code and look for uses of README/changelog (I think this may be done in the future for other functionalities and then we can reconsider). Perhaps there was no extra-doc-files initially and only extra-source-files?

@philderbeast
Copy link
Collaborator

philderbeast commented Jan 8, 2023

Browsing hackage would be a lot nicer if everyone would upload their READMEs.

I used to upload readmes but sometimes their rendering on hackage was not what I wanted so I removed them. I think that is OK if the package description is good and there's a link to the source-repository or homepage where the readme is well rendered.

@mergify mergify bot closed this as completed in #8657 Jan 23, 2023
@wismill
Copy link
Collaborator

wismill commented Jan 24, 2023

@ulysses4ever A warning for changelogs has been added in #8657. However this issue should maybe be kept opened for further discussion: it would require fine-grained selectionable warnings to implement an exhaustive check.

@Mikolaj
Copy link
Member

Mikolaj commented Jan 24, 2023

Good idea. Reopening.

@Mikolaj Mikolaj reopened this Jan 24, 2023
@ulysses4ever
Copy link
Collaborator

Thank you, that works for me!

@andreasabel
Copy link
Member

@ulysses4ever Do you really want to keep this issue open when its OP has been addressed? Maybe it would be cleaner to open a new issue with the things you find are lacking still. That would save one from reading through a lot of now irrelevant comments...

@ulysses4ever
Copy link
Collaborator

@andreasabel I agree that a new issue with an updated goal would be much more helpful. I don't have energy to act on this at the moment though.

@ffaf1
Copy link
Collaborator

ffaf1 commented Feb 23, 2025

I can do it.

@ulysses4ever
Copy link
Collaborator

That would be awesome, @ffaf1 !

@ffaf1
Copy link
Collaborator

ffaf1 commented Feb 23, 2025

Done!

@ffaf1 ffaf1 closed this as completed Feb 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment