ES devs and testers, this tool is for you!

meleu

@Hex Why don't you at least put RetroPie-Setup scripts at your home dir? There's no need to install all emulators/etc, but it would make you able to use the script...

Zigurana

@meleu
Aww man, you are the best! You've certainly risen to my challenge, superb!

I can think of only one improvement : to show the latest commit-date of the dev-branch, as well as the latest commit-date of the installed version of that branch, so users can see if they are up-to-date or not.

A Former User

Submitted a pull request cleaning up some of the display text.

meleu

Changelog

added the Update "es-tests.sh" script option in the main menu.
added script version to the backtitle (it'll be named with Greek letters' name).

Please, get the script via wget again and then you'll be able to update using the update feature from now on.

spruce_m00se

@EctoOne do you have a heatsink on the pi?
I have mine in a 3d printed mini nes case, and it only overheated on me twice, once when I was using the ds4drv driver, that just caused a constant overheat, and once when playing with overclocking and the votlage setting, I reduced it to 4.5v i think and now it runs cool "ish"

that being said I live in DUBAI! where it is mega mega hot. I run the pi in an ambient of 27 - 28 C at night when the AC is off, playing psx games and it hasnt ever overheated.
maybe you have something running in the background causing it to over heat?
I also have a KODI box which is used almost all day, again in say 25 - 27C and it never has problems overheating either, it has a small alu heatsink on it. no fan because I found the fan noise to annoying.

meleu

@Zigurana said

show the latest commit-date of the dev-branch, as well as the latest commit-date of the installed version of that branch, so users can see if they are up-to-date or not.

I started to think about ways to implement such feature, but then I realized that it would solve an already solved problem. As far as I understood you want to prevent the user spending time downloading/compiling unnecessarily. Am I right?

I made this tool acting this way: if the tester tries to build/install an up-to-date repo/branch, it won't be very time consuming.

Why?

Two reasons:

The script downloads the source files using the gitPullOrClone function from RetroPie-Setup helpers.sh, and it won't download everything again if the local repo is already up-to-date. Thanks to the RetroPie-Setup modularity I could use that function and not "reinvent the wheel".
The script gives the option to omit the make clean before make, then only those files that were changed and their dependents are compiled again (actually the script gives the option to not omit make clean, then I think we can consider this omition the default option). Thanks @Hex for this simple but wonderfully useful tip.

meleu

Hey testers! There was a bug in the script when you were trying to set the official RetroPie ES as the default one (the C option in the main menu). I've just fixed it. So, please, update your scripts.

If you used that feature to set the official ES as the default one, probably your ~/RetroPie-Setup/scriptmodules/supplementary/emulationstation.sh is non-existent/invalid. Here is how to fix it:

cd ~/RetroPie-Setup/scriptmodules/supplementary
rm emulationstation.sh
wget https://raw.githubusercontent.com/RetroPie/RetroPie-Setup/master/scriptmodules/supplementary/emulationstation.sh

Thanks and sorry for the inconvenience.

meleu

ANOTHER UPDATE

A small improvement to prevent problems as pointed by @TMNTturtlguy here.

Current version: delta

lilbud

@meleu said in ES devs and testers, this tool is for you!:

Current version: delta

Was this an intentional, or unintentional Power Rangers reference?

meleu

@lilbud it's an intentional reference to the Greek alphabet :-)

Hex

@meleu I have a few more ideas. Should I post them here?

meleu

@Hex PLEASE DO IT! :-)

Your tips are always very useful! You can also submit PRs if you prefer to write code than sentences and paragraphs (no need to do exhaustive tests, just submit the code and I test it before merge).

Hex

@meleu

A few changes that I have finished :

Replaced gitcloneorpull/gitpullorclone for my tweaks.
Added launch menu
Removed default Install menu (will bring back (only on Pi) after testing)
Changed all spaces to tabs
Added dynamic processors for make (Faster builds on multicore processors)
Added warning to Launch menu if Launching without building
moved compilations to build directory.
started removing dependence on Retropie scripts. (in works)
Only use rpSwap if running on Pi 1/Zero
Updated version to Zeta, skipping Epsilon (merging build) as you were going to incorporate my git tweaks and would have released it as Epsilon build.

Will these do? I might add some more. User requests are welcome

meleu

@Hex Those are great additions! Will you submit a PR?

pjft

I think rpswap is also used in other Pi versions in RetroPie setup. Surely it's not mandatory but unless there's a clear drawback do we need to remove it?

Hex

@pjft rpSwap does nothing if Ram > what is asked (512). Pi 1 and Zero are the only two that need rpSwap.

Hex

@meleu I would submit it tomorrow morning. Its late here. Should I submit PR with version increment? Zeta or Epsilon?

meleu

@Hex Epsilon, I didn't have time to implement the git tweaks yet. Planned to add it tomorrow.

I'm now in the middle of a tweaking Carbon theme based on what we were talking about in the @TMNTturtlguy 's post :)

meleu

@Hex regarding to rpSwap, I think RetroPie-Setup does a good job about deciding if it really needs more swap: https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/helpers.sh#L285-L313

But as we want to remove the dependence on those scripts, you can go ahead with your code.

I promess I'll organize the script and let it more readable, modularized a easier to improve. ;-)

Hex

@meleu The goal of removing dependence on Retropie scripts is so that you can run it on Linux systems which neither needs those scipts nor the installation menu