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

Questions about dyninst catalog entry #31

Open
bernhold opened this issue Dec 27, 2024 · 1 comment
Open

Questions about dyninst catalog entry #31

bernhold opened this issue Dec 27, 2024 · 1 comment
Labels
Member: STEP CASS member org software catalog Issues related to the software catalog -- content or presentation

Comments

@bernhold
Copy link
Contributor

bernhold commented Dec 27, 2024

Downloads should not link to a repository if you are also providing the same URL for a Repository

Documentation link looks like a CHANGELOG. That document includes a section pointing to Manuals. Is it possible we could link directly there? (I don't see an id attribute currently, but maybe one could be added?) There are multiple manuals. We could list all of them, though that might be tedious, and hard to maintain.

Modified name to remove extra words.

Incorporated "binary" into `description, removed period

@bernhold bernhold added the software catalog Issues related to the software catalog -- content or presentation label Dec 30, 2024
@bernhold bernhold added the Member: STEP CASS member org label Jan 13, 2025
@kupsch
Copy link

kupsch commented Jan 15, 2025

@bernhold, for the documentation, I added an anchor to the Manuals section of the latest release. The following URL will be stable to display the 6 Dyninst manuals:

If you want direct links to the 6 manuals (that potential will requires more maintenance if the number or names of the manuals change), the following 6 URLS will link the current manuals:

Dyninst does not distribute binary packages, the source for the latest release can be cloned from github, or users can use the github generated source archives in zip or tar fornat on the bottom of the release page. So I see two options:

  1. Remove the download link and just leave the github link
  2. Use the anchor I added to end of our release page markdown that will position the web page to Assets section containing the source archives: https://github.com/dyninst/dyninst/releases/latest#assets

Let me know if there is anything else you need from us or questions I could answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Member: STEP CASS member org software catalog Issues related to the software catalog -- content or presentation
Projects
None yet
Development

No branches or pull requests

2 participants