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

Display package CHANGES file #733

Closed
samoht opened this issue Aug 8, 2013 · 4 comments
Closed

Display package CHANGES file #733

samoht opened this issue Aug 8, 2013 · 4 comments

Comments

@samoht
Copy link
Member

samoht commented Aug 8, 2013

Extracted from #466

Targeted for outgoing as it is not clear to me how this can be done properly.

@yami-no-ryuu
Copy link

+1 vote

@dbuenzli
Copy link
Contributor

FWIW the packages that I packaged myself install README.md and CHANGES.md in doc.

opam info PKG could try to look for these files and display them if they are present. Maybe change the synopsis of info to something like (opam info [OPTION]... [KIND] [PATTERNS]... where KIND can be:

  • pkg (default), current info output
  • doc, ls the doc directory of the package (full paths)
  • readme, look for a README.{txt,md,pdf,ps} file and display it in a viewer.
  • changes , same as readme but with CHANGES
  • api, open api docs in a viewer.

To avoid overloading opam this could also be provided via another tool like opam-doc (well that name is already taken). A tool that does that kind of thing quite well is texdoc for TeXLive, try texdoc texdoc for an explanation, however it does not really handle standard entry points like CHANGES well imho.

@dbuenzli
Copy link
Contributor

To avoid overloading opam this could also be provided via another tool like opam-doc (well that name is already taken).

odig basically does this. It works only with text files but allows to access them in your terminal or in our browser.

@dbuenzli
Copy link
Contributor

Here again following #1900 (comment) I think this can be closed.

@rjbou rjbou removed this from the Next milestone May 20, 2020
@dra27 dra27 closed this as completed Oct 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants