Update Fedora section of the README.md file

[dejlek]

After discussion from the following PR ( #4362 ) I have finally found time to make a PR to update the Fedora section of the README.md file. I actually use those instructions myself from few different Fedora and Amazon Linux 2023 machines.

Here is an example of installing lazygit from the Copr:

» sudo dnf install lazygit
Updating and loading repositories:
Repositories loaded.
Package                                                              Arch        Version                                                              Repository                                                  Size
Installing:
 lazygit                                                             x86_64      0.48.0-1.fc41                                                        copr:copr.fedorainfracloud.org:dejan:lazygit            21.5 MiB

Transaction Summary:
 Installing:         1 package

Total size of inbound packages is 6 MiB. Need to download 6 MiB.
After this operation, 22 MiB extra will be used (install 22 MiB, remove 0 B).
Is this ok [y/N]: y
[1/1] lazygit-0:0.48.0-1.fc41.x86_64                                                                                                                                          100% |   3.7 MiB/s |   5.7 MiB |  00m02s
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[1/1] Total                                                                                                                                                                   100% |   3.7 MiB/s |   5.7 MiB |  00m02s
Running transaction
[1/3] Verify package files                                                                                                                                                    100% |  52.0   B/s |   1.0   B |  00m00s
[2/3] Prepare transaction                                                                                                                                                     100% |   3.0   B/s |   1.0   B |  00m00s
[3/3] Installing lazygit-0:0.48.0-1.fc41.x86_64                                                                                                                               100% |  44.9 MiB/s |  21.5 MiB |  00m00s
Complete!

[stefanhaller]

Happy to merge this if it's better than what we had before.

But can I ask how determined you are to keep this up-to-date? When looking at the source repo of the RPM spec, it seems that a lot of lazygit releases were skipped.

[dejlek]

Absolutely valid question. I do update the SPEC file when I notice when there is a release. I did not have time to look if this process can be automated but that is definitely in my TODO list. lazygit is at stage where there is everything I need, so it is not that I eagerly look forward to new release hoping for some bugfix to be there, like is case with some other tools. :) Experienced RPM user will know how to use the code from my lazygit RPM spec repo (link to it is in this PR) to build lazygit RPM package from any lazygit release.

What we had before was an unmaintained COPR with latest lazygit RPM package being v0.47.2-1, which is why #4362 was made, and which is why I forked that code and made it up-to-date.

[stefanhaller]

Honestly, that sounds a little bit like we might be stuck at 0.53 from now on, which doesn't sound a lot better than being stuck at 0.47.2.

Experienced RPM user will know ...

Yeah, but isn't it even easier to build from source then? Or to install from one of the tarballs of our release page.

I don't know, an earlier suggestion was to remove the link entirely and recommend to install from our binary release instead, like we do for Ubuntu. I'm actually slightly in favor of that approach if there's any risk that this new RPM repo goes stale again too.

We have regular releases now every month (always on the first Saturday of the month). If you are unsure whether you will be able to keep up with that, I'm hesitant to merge this.

Automating it sounds good though. We do this for the homebrew package, and if you can find a way to do that for your repo, that would be great.

[dejlek]

We are at 0.54.0 at the moment actually (see: https://copr.fedorainfracloud.org/coprs/dejan/lazygit/builds/)

If you do not want to merge this, then I suggest you merge #4362 instead and close this PR, as there is no point to keep it open.

I will keep my COPR up to date whenever I see there is a new lazygit release, and as I said above I will look into ways to automate this so it is possible that in the future we may not see gaps in the releases. Anyway - up to you!

[stefanhaller]

Ok, I'll merge this; if we see after a few releases that this tends to fall behind, we can still reconsider and remove the link then.

It seems to me that subscribing to our releases page should be a fairly reliable mechanism to get notified of new releases; could I ask you to do that? Maybe that's all the "automation" we need.

[dejlek]

👍 I have already looked at ways to do the automated notification and automated RPM SPEC update and build. Until the automation is done I will do as you say and subscribe to be notified of lazygit releases.