1.19 nightly flatpak vs 1.18

[Atreides]

I have the former and was wondering if the 1.19 nightly is roughly the same as the official 1.18? I can download 1.18 addons into 1.19 so it seems like it. The main difference I know of is that 1.19 has it's own MP server so I can't play 1.18 MP online.

Trying to figure out whether I really need 1.18 if I have 1.19... do I? (aside from the MP problem)

I don't want to overwrite my 1.16 stable flatpak with 1.18 stable flatpak at this time.

[gnombat]

There is probably not much difference at this point, but 1.19 will diverge further and further away from 1.18 as time goes on...

[Atreides]

I know, that's why I could just stop updating 1.19 for a while. I do it manually as with all updates.

[gnombat]

You might want to use flatpak mask to prevent it getting updated by accident.

[Atreides]

You might want to use flatpak mask to prevent it getting updated by accident.

Oh that sounds neat. However I checked and I don't have that. Using flatpak 1.2.5 and I'm guessing that's in a newer version. Thanks for the tip though I'll use it when I get a newer version eventually.

[gnombat]

It seems flatpak mask requires at least Flatpak 1.5.0.

[Atreides]

Hmm, when 1.18.1 is released I presume 1.19 master would include those changes so actually I should update 19 whenever a new 18 version is out.

[gnombat]

Well, by that time 1.19/master may contain other changes, too, possibly changing in ways which are incompatible with 1.18.

Early in a release cycle is usually when developers start breaking things with reckless abandon working very hard and making a lot of enormous improvements to the code, so the master branch can be somewhat unstable at this time.

[Atreides]

So 1.19.1 would not be compatible with 1.18.1 you mean? Hmmm yes I think I understand, the 19.x isn't just a mirror of 18.x plus a few changes between each .x version. It will now diverge from it more and more. However it would still need to be based on 1.18.x only that over time more and more beta features are added.

Argh. Well I'll have to find some other way to preserve my 1.16.11 copy. I've already looked into compiling (yech!), appimages (out of date) and debian official packages (some hope there when I upgrade to Deb 11 I'll have access to a 1.16.9 backport which I checked isn't majorly worse than 1.16.11).