[IMPROVEMENT] configurable period of skipping already updated apps

[bitoolean]

trafficstars

Please confirm these before moving forward.

• [x] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
• [x] This improvement refers to an existing feature. If you want to suggest a new feature, please use this template.
• [x] This improvement is not a bug. If you want to report a bug, please use this template.

Describe the improvement

Honestly, I'm asking for this mainly as a workaround to #1557 (Only show or visualize major updates based on semver) (and #1110 Update notification filter based on app version) requests not being addressed since these constant superfluous "update" notifications are tiresome and bothersome. - You'd think there would be such an optimization somehow included already so that a package is not re-checked for updates too often. I, personally, do not care to update a package every day. I do acknowledge that there may be situations when a fix is immediately available after a major release. Still, I'm tired of these, for example, build number updates of ungoogled Chromium (the only Scoop bucket I could get it from)... I don't care about those - the program itself won't have changed, so I shouldn't need to have to act on that every time. Instead, there should be an option to ignore that build number only update, or to set a frequency / period by which the same package shouldn't be checked for updates at least (ideally, per package). But setting the global frequency of checking for updates isn't what I'm looking for, because I still want to know if Firefox got an update this minute after another program got updated last hour / yesterday. Is there a way to bump the original issues or vote on them?

Forgive my tone this is merely a request but I just don't get why the requests didn't get more traction. I do love this piece of software to death and I might get a bit excited.

Describe how this improvement could help users

I thought this would be obvious but it seems it is getting ignored for some reason but I think this is relevant to many people to warrant some (more!) priority. I do understand and aknowledge this is something that the package manifest maintainers are also responsible of, and thus the end user as well, but then there are things like WinGet which I don't have any control over (and it does happen there too).

[marticliment]

Forgive my tone this is merely a request but I just don't get why the requests didn't get more traction.

My time is limited, and I tend to prioritize fixing bugs/issues that affect more people. Nevertheless, please keep in mind that they have not been forgotten.

[mrixner]

There is a "skip minor updates" or something similar in the installation options for the package (in this case, ungoogled chromium), which might accomplish what you are asking, as well as a "pause updates" option in the package context menu, which isn't as good of a solution but is still there.

[bitoolean]

@mrixner gee I missed that. Thank you so much! I wonder how the other threads missed it too (unless I missed that in there too). Thank you! This might just do away with this issue for me and then maybe this issue wasn't as big a deal after all and Marti could just close it. Thank you for your time and patience guys.

[mrixner]

Can you point me to any old threads thst could be resolved? It was added recently and I didn't do a comprehensive search of issues it would close 😉

[bitoolean]

@mrixner I just meant the two related request-type issues I linked. I didn't see that "skip minor version updates" mentioned there either.

[mrixner]

Sorry, I didn't see those... Thanks!