dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

devel-docs: add a tip for testing an older GIMP version with flatpak. 

Flatpak repositories can store successive builds (up to 20 in the
Flathub repository in particular), even though by default it installs
only the last build.
I added in `debugging-tips.txt` the commands to search for and
explicitly install an older build of our official GIMP build. This can
be useful to compare some behaviorial changes as reported by users,
without having to re-compile old commits just for a quick test.
This commit is contained in:
Jehan 2020-06-01 17:21:29 +02:00
parent 3991220a9d
commit 6449dd7c14
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
devel-docs/debugging-tips.txt
View File

@ -96,6 +96,28 @@ odd minor version) pop up a debug console at start.
If you are building stable versions of GIMP for debugging and want this
debug console as well, configure with `--enable-win32-debug-console`.
## Testing older GIMP versions ##
A useful trick when you want to quickly test a specific GIMP older
version (e.g. to confirm a behavior change) is to install it with our
official flatpak. The flathub repository stores past builds (up to 20 at
the time of writing). You can list them with the following command:
```
$ flatpak remote-info --log flathub org.gimp.GIMP
```
Each build will have a "Subject" line (a comment to indicate the build
reason, it may be just dependency updates or build fixes, or sometimes a
bump in GIMP version) and a commit hash. When you have identified the
build you want to test, update it like this:
```
flatpak update --commit=<hash-of-build> org.gimp.GIMP
```
Then just run your older GIMP!
## Debugging icons ##
See file `devel-docs/icons.txt` to learn more about our icons, and in