gdu@5.1.0: Add manifest

[rashil2000]

Disk usage analyzer with console interface written in Go

Ref: https://github.com/dodorz/scoop/blob/master/gdu.json

[rashil2000]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

gdu

• Description
• License
• Hashes
• Checkver
• Autoupdate

[telenieko]

Note that a PR for gdu is already open on ScoopInstaller/Extras#6098
Not submitted to Main because:

Regarding the criteria for inclussion in the main bucket:

I do not think this is a reasonably well-know and/or widely used developer tool. The project is relatively new.

[rashil2000]

How exactly does one measure 'popularity'? If we go by GitHub stars, gdu is more popular than a similar tool called dua (which is already in main bucket), and is just a year younger.

I don't think popularity/age is the problem. This repository is effectively defunct, just look at the amount of trivial open PRs.

[telenieko]

There is no clear guidelines as far as I know.

I tend to check stars, stack overflow, or Google search results.

In any case I personally default to Extras

[rashil2000]

Yeah, at least that one seems to be regularly maintained, for now.

[rashil2000]

@stevehipwell I suppose you have merge rights now, could you please review this simple age-old PR?

[stevehipwell]

@rashil2000 please update to the latest version and add a hash capture to autoupdate. I'll review the installer block after you've made the other changes.

[rashil2000]

Sorry I don't know how to put hash in the autoupdate field, could you point me towards an example?

[stevehipwell]

Please see suggestions for the updated version, how to use a different shim name and how to use hashes.

[rashil2000]

@stevehipwell made the changes, let me know if they're fine

[rashil2000]

@stevehipwell Just wanted to ask something. This repo was inactive for a long while (7-8 months), and it seems to have become active again. That said, I've had some CLI tools manifests with me for a while (all of them fit the Main bucket's criteria), I was holding myself from sending any PRs. Should I open a PR for each one of them (8-9 manifests), or a single PR would do?

[stevehipwell]

There have been a couple of new maintainers added (see #2403). For me I'd strongly prefer a single PR for each tool to keep the commits consistent and tracable.

[rashil2000]

Ah, thanks for the heads up!

Will do as you say.