bbonev
commented
1 year ago I did ask @blueness to do that long ago.
The original plan was (still is) to keep the old place for historical reasons but also include a link and a message that it is deprecated/archive.
Thanks for raising the topic.
Hey guys.
Today (and yesterday) I am compiling a new LFS from scratch. \o/
So far it all works.
I am now at eudev:
https://www.linuxfromscratch.org/lfs/view/stable/chapter08/eudev.html
I did notice it wanted eudev-3.2.11.
I was at eudev-3.2.10.
So I used my local update script. It can infer the new URL and checks remotely via curl/wget for changes. So I kind of like "static" URLs such as:
https://dev.gentoo.org/~blueness/eudev/ https://dev.gentoo.org/~blueness/eudev/eudev-3.2.10.tar.gz
As you can see version 3.2.10 is there.
But LFS uses 3.2.11 so my epic hobo-dev thought was "ok, they use a higher version so ... it must be hosted elsewhere!"
Then, being the simple man I am, I did an epic "google eudev github" where "google" is a ruby commandline script for google search.
Anyway. I then found the repository here. I then looked at the /releases and, lo and behold, I found the new eudev:
https://github.com/eudev-project/eudev/releases/download/v3.2.11/eudev-3.2.11.tar.gz
I will compile this soon for my LFS.
But, if you look carefully, the homepage of eudev lags behind, e. g. version 3.2.10 versus 3.2.11.
I believe the reason why that is so is because nobody maintains the homepage or perhaps whoever does, lags behind or may be inactive.
I have two proposals, independent sort of. Please pick an appropriate one:
(1) Perhaps it may be easier to deprecate the old homepage, and instead link to the github eudev homepage IF you guys want to focus and coordinate via github.
(2) Alternatively, and perhaps the more sophisticated solution, perhaps a small python or ruby script could automatically update that homepage with the URLs (it is a simple homepage). So when a new release is made on github, that python or ruby script could run, update the homepage, and then upload on that other homepage at: https://dev.gentoo.org/~blueness/eudev/
(2) is probably the more elegant solution but it may require access by whoever can access that server/homepage and may require an additional script that generates that homepage. So (1) is probably easier.
Of course you can also do "no change", but then people may find the eudev homepage, and think that no new releases have been made for months/years. I only found that "problem" / tiny issue indirectly via LFS for instance. Otherwise I would not have known that there are newer eudevs (I don't actually use a script to track ALL changes, I only frequent other websites for this every now and then such as LFS).
Anyway I hope the above is understandable. Thank you for reading!