It's an initial implementation to give you an idea of what I was thinking and for you to tell me how bad my go is. :)
I didn't test the logic on Windows, nor BSD. For the latter I assumed it'd work the same as on Linux but maybe not.
In a few lines, this is how it works:
It parses the config.yml file at a pre-guessed location depending on the OS (it probably would be nice to allow an override on this), and gets the dev_hdd0 path from it.
It then loops on dev_hdd0/{disc,game} to get all games installed. It may include game data not quite sure yet.
This is what we talked about on reddit.
It's an initial implementation to give you an idea of what I was thinking and for you to tell me how bad my go is. :)
I didn't test the logic on Windows, nor BSD. For the latter I assumed it'd work the same as on Linux but maybe not.
In a few lines, this is how it works:
It parses the config.yml file at a pre-guessed location depending on the OS (it probably would be nice to allow an override on this), and gets the dev_hdd0 path from it.
It then loops on dev_hdd0/{disc,game} to get all games installed. It may include game data not quite sure yet.
Then back to your previous logic
Thanks!