[aur-requests] Request: libksysguard-git

[Christopher Snowhill (kode54)]

> On Mar 24, 2021, at 8:07 PM, Eli Schwartz via aur-requests <aur-requests at lists.archlinux.org> wrote:
> 
> On 3/24/21 10:04 PM, Dániel Vizy via aur-requests wrote:
>> Dear Devs,
>> 
>> I would like to request a git version for libksysguard based on
>> invent.kde.org <https://invent.kde.org/plasma/libksysguard>
>> 
>> There is a git version available: libksysguard-git
>> <https://aur.archlinux.org/packages/libksysguard-git/> ,but the package
>> source
>> and the version number are different 5.21.80_r2048.gc3de4a9-1.
>> 
>> Latest git version for libksysguard is 5.21.4 at the moment:
>> ibksysguard/commit
>> <https://invent.kde.org/plasma/libksysguard/commit/265337b6901f9170e8151412a5033c71fc79d00e>
>> 
>> I would be very appreciated for this.
>> Sincerely,
>> Dany
> 
> 
> As far as I can tell, these are the same thing.
> 
> The current libksysguard-git uses https://github.com/KDE/libksysguard/
> 
> While you proposed to use https://invent.kde.org/plasma/libksysguard/
> 
> But, the former (github) is a mirror of the latter (KDE's self-hosted
> gitlab instance) and both are owned and pushed to by the same group
> (kde.org).
> 
> Both show the same commit sha1 as the latest code.
> 
> -- 
> Eli Schwartz
> Bug Wrangler and Trusted User

I think the issue they may not be aware of is that KDE's git packages have horrible version number issues that are not entirely the blame of the pkgbuild author. In most cases, they have crappy git repo release tags. In some, a version number has to be hard coded, and then all you have left is the commit count since the beginning of history and a commit hash fragment.
>