Abstract: improve sort order in phoenicis

[Kreyren]

This is not how we organized the scripts. We should have one different script per version.

Originally posted by @qparis in #908 (comment)

---

Request

Requesting utilize existing function for sorting of scripts in $SCRIPTDIR instead of using Online, Local, Steam, etc..

Where there would be one entry for each version present alike in case of photoshop where we would have to make +- 18 scripts for each photoshop version.

Reasoning

Current is wastefull assuming that we can provide ONE scripts for each version of the engineapp presented which is much better on organization and QA.

[qparis]

Description and title of this issue is not clear enough

[Kreyren]

@qparis updated, rm your comment and mine for clarity if sufficient and re-open.

OP will be updated with more info if needed.

[plata]

Honestly, I still don't understand what this issue is all about.

[Kreyren]

@plata updated OP, better?

So that for league of legends/Photoshop for example we would have script for 9.18, 9.17, etc.. versions in

Which would make script maintainance much easier and effective + would allow more QA.

[qparis]

Honestly we don't want to go in this direction. We don't want to support every single version of every program either.
We only may want to support the major versions at the same time, and it does not justify to create an additional level of script hierarchy

[Kreyren]

@qparis disagree, lots of user might want to use different version of said software and said support is painless for phoenicis assuming that scripts would be community maintained -> More options more opportunities to contrib and enhance phoenicis functionality.

• this is GNU ethics

[plata]

For free software, I agree to @qparis. It doesn't make sense to maintain old software forever. However, I can also understand that this might be different for software where you can only use a certain version (e.g. because you bought it). In any case, there is no alternative to providing one script per version simply because the versions might need different Wine versions, settings, verbs etc. So, @Kreyren I get your point but it's not possible technically.

[Kreyren]

get your point but it's not possible technically.

that's literally what wine is doing on WineHQ -> very possible and usefull for FOSS software as well linux kernel is good example of that.

[plata]

I don't see how Wine provides scripts. If you refer to the test reports, this is handled exactly like we do it.

[Kreyren]

@plata i meant the instructions to make wineapp working on linux is the same as proposed with same reasons.

[plata]

Sorry, but that's just not true in general. Of course, there might be apps where this is the case but you cannot assume that it's always like this and therefore it is nothing Phoenicis could rely on.

[Kreyren]

it's not expected to be relied on it's expected to be compatible only.

[plata]

I don't see how this could work in a general way. If you want to implement the behavior for a certain app, do it like this: Add a preInstall step with a choice wizard where the user can select the version.