search

zom-ponks / rpcs3-gameupdater

Fetches game updates for the RPCS3 emulator
MIT License
2 stars 1 forks source link

Being able to specify which updates we want #39

Open John-Gee opened 4 years ago

John-Gee commented 4 years ago

Maybe this shouldn't be a grab all or nothing, maybe we could specify which game we want to grab for, especially for people with limited bandwidth per month.

Maybe we could also add priorities, so that the games I care for the most get updated first, and while I play them the updater can work on the rest.

zom-ponks commented 4 years ago

In GUI this is easily done, add a checkbox to any possible updates and include "select all/none" like most GUIs do to let the user easily select what they want updated.

In CLI the workflow has to be different since it's non-interactive, maybe something like args "--show-updates" to list games and IDs that have updates, and then "--update ID1,ID2" and "--update-all"

John-Gee commented 4 years ago

Supporting range, game, etc for the CLI could be nice too.

Here's an example of running 'yay' on my system, a package manager:


 9  extra/python-appdirs                      1.4.3-5                             -> 1.4.4-1
 8  extra/python2-appdirs                     1.4.3-5                             -> 1.4.4-1
 7  mesa-git/lib32-mesa-git                   1:20.2.0_devel.123592.8e5fc97be63-1 -> 1:20.2.0_devel.123639.f079c00ffc1-1
 6  mesa-git/lib32-vulkan-mesa-layer-git      1:20.2.0_devel.123592.8e5fc97be63-1 -> 1:20.2.0_devel.123639.f079c00ffc1-1
 5  mesa-git/lib32-vulkan-radeon-git          1:20.2.0_devel.123592.8e5fc97be63-1 -> 1:20.2.0_devel.123639.f079c00ffc1-1
 4  mesa-git/mesa-git                         1:20.2.0_devel.123592.8e5fc97be63-1 -> 1:20.2.0_devel.123639.f079c00ffc1-1
 3  mesa-git/vulkan-mesa-layer-git            1:20.2.0_devel.123592.8e5fc97be63-1 -> 1:20.2.0_devel.123639.f079c00ffc1-1
 2  mesa-git/vulkan-radeon-git                1:20.2.0_devel.123592.8e5fc97be63-1 -> 1:20.2.0_devel.123639.f079c00ffc1-1
 1  archlinuxcn/nano-syntax-highlighting-git  566.2c00b96-1                       -> 574.a73f290-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)```

In this case I write what I want to exclude, I can write a repo name for instance mesa-git, I can write individual numbers of packages I do not want, or a range in both ways you can see above. Of course that may be something to add, once it starts working.

Of course, your tool is not something that people would necessarily run over and over, and a GUI is likely to be more used than a CLI, so maybe that's not necessary for the CLI after all.