Hey,
I was wondering why there is no package for 2.22.0 or 2.23.0 in the Fedora repos…
Aren’t we known to be pretty up-to-date?
super out-of date
Are you serious?
Version 2.23.0 was released 18 hours ago, version 2.22.0 was released last week.
The version in the Fedora repository was released 3 weeks ago, that is really not slow for a small community application like fastfetch.
2.22.0 should at least be in testing
The package maintainers are volunteers just like we are here on the forum and they do as time permits. As with everyone in the fedora community, we have a life that we must take care of and volunteering time here or to package software is only a part of the many demands on our time.
If you would like things packaged, tested, and released faster maybe you could volunteer to assist in building and maintaining packages. Otherwise please be patient and updates are provided as fast as time permits.
2 Likes
@burningpho3nix if you want to accelerate the process and doing something good, I propose you sponsor the developer who makes the package. If you can not do it on your own (making a package), this would be a great option to participate to increase the release frequency of the application.
Someone can also volunteer for AppImage support [FEAT] List of currently unsupported package managers · Issue #1203 · fastfetch-cli/fastfetch · GitHub
1 Like
Why isn’t it packaged with an automated package generation?
Wouldn’t that make it easier?
We do use automation to make our lives easier, see packit for example. However, that does not mean that a human does not need to be involved at all. Every new release may change how the software is to be built, what files are to be included. Every new release may also change the license of the software (by including non FOSS bits, for example). Finally, every new release has to be vetted by a human to ensure it doesn’t include anything malicious, and of course to ensure that it complies with the Fedora packaging guidelines.
So, we cannot use a completely automated pipeline because there’s more to packaging than “build it however and ship it”. It can be semi-automated but still needs a human to go over the changes to vet and fix things before it can be shipped out to users.
If you want to speed up updates, you can help the package maintainer in a number of ways:
- become a co-maintainer for the package
- open pull requests to help with updates
- test the package when it hits the updates-testing repository so that it can reach other users quicker
I hope that clarifies things a litle.
4 Likes
I was considering asking that; it sounds like that that’s the biggest point of SUSE’s OBS system (some packages also use it to provide Fedora rpms).
On the other hand, I’m not sure how useful fastfetch is to be doing all this if it wasn’t done already. That, neofetch, inxi; all that is just some front-runner nice-presenting means for hardware listing that can all be manually done with lspci/lsusb/lscpu/dmesg/glxinfo that already exists on the system.
With SUSE OBS system, you still need someone to take the initiative to feed the new source to the system. I suspect that OBS isn’t that different from whatever Fedora uses to build the rpm packages.
2 Likes