-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change the application ID for the beta branch. #92
base: beta
Are you sure you want to change the base?
Conversation
It's ugly but this is the only way to not have to manually switch the flatpak branch through boring command lines. See issue #91 and flatpak/flatpak#1109.
Started test build 31190 |
Build 31190 failed |
Started test build 31208 |
Should be removed: - /app/share/doc/ghostscript/9.53.3/* - /app/share/thumbnailers/heif.thumbnailer - /app/bin/x265
Started test build 31209 |
Build 31208 failed |
Build 31209 failed |
Update build-id for version check (though it's not too important here) and the binding options, which are now different.
Started test build 31215 |
Build 31215 failed |
This can't work. You have to submit new app to flathub with new id and new git repo. |
This won't work.
Also |
We know. We have already advised people to run these commands ever since this beta branch exists. See for instance the "Flatpak additional instructions" in: https://www.gimp.org/downloads/devel/ Even in our release news, we told about these commands: https://www.gimp.org/news/2020/11/06/gimp-2-99-2-released/#beta-flatpak-available But the simple fact we have to tell about this tells it's sucky workflow because it means it doesn't integrate at all with the desktop. People who want to test the development versions don't want one or the other (or to run annoying, hard-to-remember command line in terminal). They want to use the stable one for their daily work, and be able to run the dev one on a whim. This is possible on Windows (it would probably on macOS too if our packager had packaged the dev version) but not on Linux right now and that's too bad. 😕 Anyway the current proposed trick is to use a different app ID but that will also imply we make a new repo, which is annoying for a few reasons; one of them being that now everyone already registered this beta branch and people currently using it would not get the updates for next versions and would not know why. So I'm holding back this for now. Maybe later if we add a "notification channel" in GIMP where we are able to send important messages (opt-in). I don't know, we'll see… |
@@ -1,5 +1,5 @@ | |||
{ | |||
"app-id": "org.gimp.GIMP", | |||
"app-id": "org.gimp.GIMP.dev", | |||
"branch": "beta", | |||
"runtime": "org.gnome.Platform", | |||
"runtime-version": "3.36", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recommend bump the runtime version, and all yml to beta files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's already at 40
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update this development branch, what did i mean, merge master to this branch. It's for resolves conflict
It's ugly but this is the only way to not have to manually switch the
flatpak branch through boring command lines.
See issue #91 and flatpak/flatpak#1109.