8000 Outdated info at pkgconf.org · Issue #232 · pkgconf/pkgconf · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Outdated info at pkgconf.org #232

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.

Sign up for GitHub

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

Jump to bottom
Open
Olf0 opened this issue Aug 30, 2021 · 0 comments
Open

Outdated info at pkgconf.org #232

Olf0 opened this issue Aug 30, 2021 · 0 comments

Comments

@Olf0
Copy link
Contributor
Olf0 commented Aug 30, 2021 •
edited
Loading

Basic issue

Unfortunately the information at pkgconf.org was not updated for long.
While this just provides a negligent impression for the "feature comparison" there (making one think "What is comparing and discussing long outdated versions good for?"), the real culprit IMO is the "Download (.tar.xz)"-link at the main page, which points to https://distfiles.dereferenced.org/pkgconf/pkgconf-1.1.0.tar.xz
In contrast to issue #223, one cannot easily detect there (at pkgconf.org), that v1.1.0 is long outdated.

Additional issue

Calling https://pkgconf.org/ exhibits a certificate error, because the certificate used is only valid for the domains github.com and github.io

Suggested solutions

  1. As a quick & dirty measure one may simply redirect http://pkgconf.org/ to https://github.com/pkgconf/ (or to https://github.com/pkgconf/pkgconf/).
  2. As the content of the site pkgconf.org is nice and informative (although outdated), one may update its content, specifically the "feature comparison" and the download link. If issue Displayed latest release heavily outdated and to the updated #223 is resolved (and is kept in that state by continuing to publish pkgconf releases as GitHub-releases), GitHub provides a link to the "latest" release, which can be used for the download link;
    alternatively a link to the releases page at GitHub might be used, which alleviates the need to pay attention.
    Then these two web-pages shall also be moved to a place, which provides a maintained x.509-certificate infrastructure (for https), for example, github.io
    Side note: GitHub is offering every project it hosts a page hierarchy at github.io (configurable in the project settings), and pkgconf.org then should redirect there.

P.S.: When choosing the suggested solution 2, I offer to review the result, and also suggest to mention this link which nicely shows "Which distro uses which version of either pkgconf or pkg-config?": https://rpmfind.net/linux/rpm2html/search.php?query=pkgconfig(pkg-config)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Olf0
0