Outdated info at pkgconf.org #232

New Issue

2021-08-30T22:34:27Z

Olf0 commented

2021-08-30 22:34:27 +00:00

(Migrated from github.com)

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

As a quick & dirty measure one may simply redirect http://pkgconf.org/ to https://github.com/pkgconf/ (or to https://github.com/pkgconf/pkgconf/).
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 #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)

### Basic issue Unfortunately the information at [pkgconf.org](http://pkgconf.org/) was not updated for long. While this just provides a negligent impression for [the "feature comparison" there](https://pkgconf.org/features.html) (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 [http**s**://pkgconf.org/](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 #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](https://github.com/pkgconf/pkgconf/releases) 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 <sub>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.</sub> 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 in to join this conversation.