Need Help with OpenBor & Retropie-Extra (Exarkuniv)
-
@Wrestlnut said in Need Help with OpenBor & Retropie-Extra (Exarkuniv):
Also, I missed a couple of the cd ~ entries when running the initial scripts. Not sure if that makes a difference since everything seems to point to home/pi/RetroPie-Setup anyway, but I figured I would mention it just in case.
no that doesn't matter, if there was a issue it would not install the scripts to be ran to start with. if you can install it, then that part worked fine
@Wrestlnut said in Need Help with OpenBor & Retropie-Extra (Exarkuniv):
I still don't see Retropie Extra
it will not be called Retropie Extra that is just what the main folder is called that holds all the scripts that i have made/maintained.
so my question for you, is what version are you tring to install. there will be 2 different ones, in the install menu, one that says
openborthat one will install the rom folder in to the ports folder, so you need to lookroms/ports/openborthe version that is in Retropie Extra is called
openbor-v6510and that one will install a folder into the roms folder so thisroms/openborto test i deleted the
roms/openbor, removed the system by using the remove function in the install menu, and then install it again from the same menu, and it also remade that folder when it was done.not sure what is going on for you, from what i can test the
openbor-v6510is working correctly -
@ExarKunIv IT'S WORKING!! I did exactly as you described and deleted roms/openbor, removed openbor-v6510, reinstalled from source, and it automatically added roms/openbor back in. I then added he-man.pak and restarted ES, and lo and behold it worked. Apparently the roms/openbor folder I created manually did not have the same relationship to the emulator as the system-created version.
I cannot thank you enough, EK! Also a special shoutout to @mitu and @sleve_mcdichael. I appreciate everyone's fast and detailed responses. You all helped me recapture a big part of my childhood today . Now it's time to go defeat Skeletor and his evil henchmen!
-
@mitu said in Need Help with OpenBor & Retropie-Extra (Exarkuniv):
Maybe we can relax this check and get the modification date of the file, if
gitdoesn't find the last modification of the file.And this quick change to the Extras install will preserve the modules' timestamps when they are copied, so that can be accurately assessed.
-
@sleve_mcdichael said in Need Help with OpenBor & Retropie-Extra (Exarkuniv):
And this quick change to the Extras install will preserve the modules' timestamps when they are copied, so that can be accurately assessed.
That's ok, but I think it will only work after this change is added to RetroPie.
-
@mitu btw I've not merged yet as I want to test but I think I may implement this differently.
-
@mitu did I do something wrong?
$ ls -l ext/RetroPie-Extra/scriptmodules/ports/prototype.sh -rw-r--r-- 1 pi pi 1377 Jul 21 2022 ext/RetroPie-Extra/scriptmodules/ports/prototype.sh $ cat /opt/retropie/ports/prototype/retropie.pkg pkg_origin="source" pkg_date="2023-02-21T21:42:33-08:00" pkg_repo_type="git" pkg_repo_url="https://github.com/ptitSeb/prototype.git" pkg_repo_branch="master" pkg_repo_commit="12d2de8639982db12091ca37eeee9036b54f3fa7" pkg_repo_date="2020-12-20T17:42:33+01:00" pkg_repo_extra="" $ git status On branch update-package Your branch is up to date with 'cmitu/update-package'. nothing to commit, working tree clean $ sudo ./retropie_setup.sh
-
@mitu did I do something wrong?
No, but did you read my previous reply ?
EDIT: Ah, I see you're used by PR to test. Seems it's not working correctly then.
EDIT2: Seems the update trigger is also influenced by the commit hash from source repo declaration - without it works fine. Either remove the commit (keeping the branch) or add the full commit hash - see if it works afterwards.
-
This post is deleted! -
@mitu said in Need Help with OpenBor & Retropie-Extra (Exarkuniv):
EDIT2: Seems the update trigger is also influenced by the commit hash from source repo declaration - without it works fine. Either remove the commit (keeping the branch) or add the full commit hash - see if it works afterwards.
Indeed, with the full commit sha, or none, it works:
So I wonder, then, how do the "native" RetroPie modules manage to still work it using the truncated sha?
rp_module_repo="git https://github.com/scummvm/scummvm.git master a9418f8f"
-
@sleve_mcdichael said in Need Help with OpenBor & Retropie-Extra (Exarkuniv):
So I wonder, then, how do the "native" RetroPie modules manage to still work it using the truncated sha?
-
@mitu oh, so if it's exactly 8 characters, then...?
Huzzah!
EDIT: I've been using seven just because that's what GitHub likes to show me:
Is this good? https://github.com/s1eve-mcdichae1/RetroPie-Setup/commit/802ddfd0ed7ec31d483e3468d76fb8dd4896276a
Seems to work on quick test. Does it break anything else?
What's the smallest a commit sha can be and still work? Any reason not to just make it
-gt 0?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.