RetroArch update from source isn't bleeding edge

meleu

I see in retroarch.sh scriptmodule commit history that the RetroArch sources version is hardcoded since 4-Feb-2017 (being updated as the upstream releases supposed stable versions).

Isn't the intention of the "Update from source" to get the bleeding edge version anymore?

I think it's to avoid issues related to new-and-not-very-well-tested features for those users on a platform that doesn't have pre-compiled binaries (e.g.: x86). Also, I remember that @BuZz said in Idea for experimental: Install Arbitrary ES-branch:

retropie-setup is not supposed to be some development / testing gui.

But man... The "Update from source" option for getting the bleeding edge RetroArch was very handy. Can we have this as an option?

lilbud

I believe this whole thing is due to this commit, though I may be wrong.

https://github.com/RetroPie/RetroPie-Setup/commit/9b5c738b1447069fb7b4f4af11571394b65f2e71

meleu

@lilbud As far as I understood it started here: https://github.com/RetroPie/RetroPie-Setup/commit/6e3e5299c77797404434c979ed88f8a0c127b938

edmaul69

@meleu i keep seeing this being said, can you tell me what bleeding edge means?

meleu

@edmaul69 said in RetroArch update from source isn't bleeding edge:

can you tell me what bleeding edge means?

From wikipedia:

"Bleeding edge technology is a category of technologies so new that they could have a high risk of being unreliable and lead adopters to incur greater expense in order to make use of them.

In our context it means the really latest version of a software, and probably not very well tested.

BuZz

@meleu it was too much work to maintain as it broke too often. Check commit history :-)

So the answer is no, at least for now.

Some platforms are source only with RetroPie. Not all source builds are bleeding edge. Quite a few are not.

meleu

@BuZz Wow!, it must be hard to keep track of all upstream updates! Thanks for your hardwork to keep all this stuff running fine! :-)

Regarding my request, no problem. Anyway deleting that hardcoded branch in retroarch scriptmodule to get the master one isn't that hard... :-)

I was about to edit the RetroAchievements part of the wiki talking about a new feature added to RetroArch yesterday but I think it's better to wait for v1.6.2. before that.

Cheers!

meleu

@buzz what do you think about adding another scriptmodule for the bleeding edge RetroArch? Just like you did for emulationstation. Maybe a retroarch-dev.sh...

It would be useful to get/test really new features/fixes.

If you agree I can submit PR for that.

BuZz

@meleu I have a more generic plan for modules, but needs some more planning and work. Es-dev was a quick fix due to breakage, but I'd rather not do more.