Create a metapackage for latest git version available in IUS

[tukusejssirs]

Some time ago, I have created a script that installed git2u-all from IUS repo. Now it does not work as there is no package with that name.

Currently, we have two packages one could install: git222-all and git224-all. As I see it, it looks like that you have chosen to include the git version into the package name. I think that is incorrect, but do what you think is the best.

Besides removing the version number from the package name, I see another solution: create a metapackage (e.g. git-ius or whatever you think is the best name) that would always install the latest package available in the IUS repo.

[carlwgeorge]

Now it does not work as there is no package with that name.

There is no package with that name because the package was renamed to git216 to reflect the fact that it was staying on the upstream 2.16 branch. When the most recent git CVE was announced, upstream did not release a fix for the 2.16 branch, effectively declaring it EOL. Per standard IUS practice, once the branch was EOL upstream, we archived the packages to reflect the fact that they are no longer maintained.

As I see it, it looks like that you have chosen to include the git version into the package name. I think that is incorrect, but do what you think is the best.

That's how IUS works. The only reason the previous package was named git2u (major version only) was because we incorrectly believed that upstream was only maintaining major version branches. You can see that we always had the relevant version in the package name, it's just that the relevant version changed from 2 to 2.16.

Besides removing the version number from the package name, I see another solution: create a metapackage (e.g. git-ius or whatever you think is the best name) that would always install the latest package available in the IUS repo.

No. IUS doesn't do this for any other package. One of the goals of IUS is to allow you choose an upstream branch, get updates to the latest of that branch, but not update to the next branch until you explicitly choose to. Alias packages run contrary to that. Even if we did decide to go that direction, doing it for just one group of packages doesn't make sense, it would need to be all or none. While upgrading to the next branch continuously may typically be fine for git, it definitely isn't fine for other IUS packages. I covered this when we originally decided to keep git2u on the 2.16 branch.

You can accomplish your goal by running one of the following.

yum install /usr/bin/git

yum install --exclude git git