@mitu said in lr-mame & lr-mess binaries:

Latest commit on the upstream repository is from May, 27 - I think the binaries are pretty close to the 'lastest version'. You can check when the binary was built and from which commit, just to compare with the upstream repo (https://github.com/libretro/mame).

Ah, I see that now. Looks like they're dealing with one heck of a pull request. I'll keep an eye on the upstream repo. Cheers, and thanks!

@tavuntu

In my last post I had to get a bit acquainted with DietPI.
I was thinking there wasn't a normal user so I added user "pi" now.
I overlooked that a normal user "dietpi" already exists.
So we user "dietpi" is usable in the future.

Anyway, I did somewhat a new RetroPie-Setup as user "dietpi" again.
Everything seems to work ok now and Emulationstation works too.
The desktop parts at the right and the left when starting a libretro core, that I described in my earlier post, are gone now too.

The experience is just like the normal "Debian 11 Bullseye / 32 bit" with mate desktop installed.

Conclusion :
After making a fresh OS you have to :

login as "dietpi" get RetroPie patch the sdl2.sh, system.sh and emulationstation.sh files install sdl2 install the core, main and other packages enjoy

Edit :
Too bad, I have no sound from hdmi, it seems some audio packages could be missing ;-(
Jack output works though. ;-)

Binary sources are here: https://github.com/RetroPie/RetroPie-Setup/blob/c39ad0533de9b6851ab6dab9c57437e97874f94d/scriptmodules/system.sh#L64-L87

They are hosted at files.retropie.org.uk/binaries, but it's not browsable.

@buzz yes please do let me know when you do so. I'll keep on the lookout as well. I understand wanting to keep things central (don't want malicious code uploaded in binary form run on peoples devices).

Glad to hear that its on your mind though (binaries for additional systems/architectures would be much appreciated).

I guess another alternative would be changing the scripts so more that one binary repo could exist (user could supply one through some config)... though that is a niche use case especially if you plan on expanding the number of devices you build for yourself in the future.

@mitu for what I need, it seems this does the trick:

~/RetroPie-Setup/retropie_packages.sh pkg depends ~/RetroPie-Setup/retropie_packages.sh pkg install_bin

Thanks for the info. I will look into the script issues you mention and will move it to optional when I've tested.

Such option doesn't exist right now, but you can use the auto-update just for the sections which always have binaries - i.e. excluding experimental. The experimental section recently started providing binaries, so that would work for most of them - my guess you have the extra repository enabled and those don't have binaries.
If you open a package from the menu, it will detect if there is a binary update available and you can choose to update or not. Sure, it's just a workaround, but how many experimental packages do you have installed ?