ES devs and testers, this tool is for you!

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

Hex

Can someone running Retropie on Pi 1/Zero let me know the output of this command uname -a

meleu

@Hex oh, I'm not in the same city as my raspi1...

Maybe @obsidianspider or @edmaul69 can help with this...

meleu

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

@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

ASFAIK the only thing needed to change the default emulationstation is one single line on /usr/bin/emulationstation. The line that looks like this:

"/opt/retropie/supplementary/es_pjft_retropie-screensaver-merge/emulationstation.sh" "$@"

We can remove the dependency very easily a simple sed trick can deal with it. :-)

I reused the code to finish a usable version of the script as soon as possible and don't lose the "timing" in the @Zigurana 's thread. :-)

meleu

@Hex said in Help testing: Random Video Screensaver on Main Branch:

To combine all of theme in one sentence you can have the command as such :
git pull || git merge --abort && git pull -X theirs

The || ensures that git merge --abort && git pull -X theirs only runs if git pull fails

Oops. It didn't work as expected. Look what I mean:

$ echo bla || echo ble && echo bli
bla
bli

Got it?

But there's no problem, I adjusted it here:

if ! git pull; then
    git merge --abort && git pull -X theirs
fi

I'm making the git tweaks now (and creating my own version of gitPullOrClone), but you can still name your version as epsilon. :-)

edit: git tweaks done.

edit 2: I borrowed rpSwap code from RetroPie-Setup's helpers.sh, and now helpers.sh is not a dependency anymore.

lilbud

@meleu Damnit, I thought you were making a Power Rangers: S.P.D, Space Patrol Delta.

Hex

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

@Hex said in Help testing: Random Video Screensaver on Main Branch:

To combine all of theme in one sentence you can have the command as such :
git pull || git merge --abort && git pull -X theirs

The || ensures that git merge --abort && git pull -X theirs only runs if git pull fails

Oops. It didn't work as expected. Look what I mean:
$ echo bla || echo ble && echo bli
bla
bli
Got it?

But there's no problem, I adjusted it here:
if ! git pull; then
    git merge --abort && git pull -X theirs
fi
I'm making the git tweaks now (and creating my own version of gitPullOrClone), but you can still name your version as epsilon. :-)

edit: git tweaks done.

edit 2: I borrowed rpSwap code from RetroPie-Setup's helpers.sh, and now helpers.sh is not a dependency anymore.

it should be echo haha || ( echo hehe && echo hoho )

I forgot those brackets.

TMNTturtlguy

@Hex ha ha he he ho ho, can we add fe fi fo fum? :)

lilbud

@TMNTturtlguy

Hex

Added features :

Install on Linux (PC)
Optimized handling ES installation.

@meleu I would like to stick to Zeta version. My changes are taking more time than expected. I would like to include all changes you incorporate for Epsilon. If and only if Epsilon is not released by then, I shall drop down to Epsilon as version. Should I post it on my repository?

How do I go about submitting PRs. You have many scripts in single repo.

meleu

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

Added features :

Install on Linux (PC)

??
I've been always using it on my Linux x86...

@meleu I would like to stick to Zeta version.

The current version is delta3(lower case), I go ahead for the next Greek letter when a new functionality is added. When adding tweaks and/or small fixes I just add a trailing sequential number.

How do I go about submitting PRs. You have many scripts in single repo.

Well, that repo should be a place for "small codes to share with friends or to make me remember some trick" as the description says. But as this script is getting a bit more serious, I've created another repo:

https://github.com/meleu/rp-testers

You can submit your PR there.

Thanks!

Hex

@meleu I have put my script here : https://github.com/hex007/es-dev/blob/master/es-tests.sh

Feel free to merge changes. I am currently busy and unable to work on this. If I make any changes I shall commit there and let you know else fork your repo once you have merged changes so there is a single copy.

EDIT : Also I have to mention that the correct word is to "skip" and not "omit" the make clean.

meleu

@Hex Phew... What a relief! I thought you were hating me because I don't indent my code with tabs!

Thanks for the English. tip ;-)

Zigurana

@meleu
https://stackoverflow.blog/2017/06/15/developers-use-spaces-make-money-use-tabs/

meleu

@Zigurana haha!
I will certainly use those data in future tabs x spaces flame wars!

cyperghost

Hey I am not using spaces or tabs!

Wait there is someone on my door ringing....
Ah the new helicopter is delivered.... I do not like used ones.

Hex

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

@Hex Phew... What a relief! I thought you were hating me because I don't indent my code with tabs!

Thanks for the English. tip ;-)

I had mentioned in one of the threads that I would be busy this week. I uploaded the code long ago. Just forgot to update it here. I apologise for that.

I am quite flexible with tabs or spaces.

Hex

@meleu I had an idea while working with this. You know how users using this script are testers only and dont contribute (git push) code (no offence to those who do). I was thinking if it would be ok to have a patch screen where users could add patches with features to their current build.

eg. I have published a simple commit that increases the font size for smaller screens. If a tester is interested they can use this patch to whichever ES they are compiling unless there is a conflict. This allows tested patches to be used by the testers customizing their builds.