| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Rename-configure.in-to-configure.ac.patch | Rename configure.in to configure.ac and add all generated files to .gitignore (cherry picked from commit 0b46d294ec30483c13a5384460fb650546a045d6) |
Michael Natterer <mitch@gimp.org> | no | upstream, after 2.0.4 | 2018-06-16 | |
| Issue-360-scripts-that-require-brushes-that-GIMP-no-longe.patch | Issue #360 - scripts that require brushes that GIMP no longer installs carved-logo.scm: apply slightly modified patch from Carol Spears which replaces hardcoding round brush names by creating a brush on the fly and setting its radius. (cherry picked from commit d2007e44aae2eae898d843eea436d94eda3e77d4) |
Michael Natterer <mitch@gimp.org> | no | upstream, after 2.0.4 | 2019-07-14 | |
| plug-ins-add-Python-2-GIMP-2-API-plug-ins-not-ported-to-n.patch | plug-ins: add Python 2/GIMP 2 API plug-ins not ported to new API. After review by Elad Shahar, then by myself, we decided these 4 plug-ins are probably not worth the effort to port them to the new GIMP 3 API (and Python 3). Either they are duplicate of existing script-fu script or of GEGL operations or they are in unfinished state. All of them were not even installed on stable builds. See isssue gimp#4368. Nevertheless as Akkana Peck (akk) points out on IRC, some of them are interesting to study, in order to know how some things can be done in GIMP plug-ins (because even with API changes, most of base code logics is reusable) and also maybe these could be improved in the future to do something actually useful or better than existing plug-ins. So I move them to gimp-data-extras. I don't add them in the build system though, because they probably should not be considered stable even in this repository. But at least code is there for whoever wants to build good plug-ins from there. (cherry picked from commit 3d11ab9ada9b7c986726bd27c0e1cf6a649a7c1f) |
Jehan <jehan@girinstud.io> | no | upstream, after 2.0.4 | 2020-09-21 | |
| plug-ins-move-py-slice.py-from-GIMP-repository-to-gimp-da.patch | plug-ins: move py-slice.py from GIMP repository to gimp-data-extras. Per polls on Twitter, Reddit, Patreon and Tipeee, most people were willing to drop this plug-ins as not being relevant anymore (247 for dropping and 63 for keeping it, so nearly 80% out of 310 participants). So let's move it to gimp-data-extras allowing it to still have a possible life, and who knows, maybe to even evolve. While doing so, adding a --enable-gimp3 flag to the configure step. With this option, the repository will look for a gimp-3.0 pkg-config file instead of gimp-2.0 and will install to the relevant data and plug-in folders. Note that data (brushes, patterns, etc.) are installed both with --enable-gimp3 and without, but the Python 3 plug-in is only installed with the option enabled, since it is not GIMP 2.x compatible. (cherry picked from commit beffc6bbca18ea7c256669cc427d416792167a44) |
Jehan <jehan@girinstud.io> | no | upstream, after 2.0.4 | 2020-12-15 | |
| Change-Javascript-to-JavaScript.patch | Change "Javascript" to "JavaScript" (cherry picked from commit 37411a93503bf87ba906e7cce50e6f196b1c7a22) |
scootergrisen <scootergrisen@gmail.com> | no | upstream, after 2.0.4 | 2020-12-15 | |
| plug-ins-move-benchmark-foreground-extract-from-GIMP-repo.patch | plug-ins: move benchmark-foreground-extract from GIMP repo. We did port it to the new API but we are doubting it is useful at all. It might have been, historically, when foreground extract algorithm was first introduced, but probably not anymore, even more as the algorithm is now implemented mostly on GEGL side anyway. So if any benchmark were to be done, it should probably be added as GEGL tests. Still we move it to the gimp-data-extras repository for being able to easily bring it back in case we missed some use. (cherry picked from commit 57710ed02f4f6e1def7484c49387324e52a7ffd6) |
Jehan <jehan@girinstud.io> | no | upstream, after 2.0.4 | 2021-04-19 | |
| desktop-move-the-AppStream-metadata-from-GIMP-repository.patch | desktop: move the AppStream metadata from GIMP repository. As far as I can see, this metadata file was added in 2017. See the (renamed recently into a proper AppStream ID) Unless I am missing something, it was created for the gimp-data-extras package, never for anything shipped within the main GIMP repo. The gimp-data-extras repo already existed back then, so I guess having pushed it to the main repo was a mistake (?). Therefore moving it to its rightful place so that this package gets proper metadata when listed in application catalogs. While doing this, also adding some initial localization. I know we are being told to drop intltool and this could be a good start to do it as the only localized data is this metadata, but I just wanted to make a very quick data move, no thinking. If anyone wishes to make the port to full-gettext (which is what various reports advises), we welcome merge requests! (cherry picked from commit 28467cb7d891874aa5b0d18d94a02dde0896a926) |
Jehan <jehan@girinstud.io> | no | upstream, after 2.0.4 | 2022-05-04 | |
| po-move-all-existing-translations-from-GIMP-repository.patch | po: move all existing translations from GIMP repository. These contains a lot more than what we need, but whatever. Better not lose the existing translations. (cherry picked from commit 5b8cfd5aa7097854e05e8f6db2b59dd583ccd03c) |
Jehan <jehan@girinstud.io> | no | upstream, after 2.0.4 | 2022-05-04 | |
| plug-ins-Port-max-rgb-filter-from-2.10.patch | plug-ins: Port max-rgb filter from 2.10 Converts the 2.10 max-rgb plug-in to GEGL and archives it here. (cherry picked from commit 46da5c1f045fafc507350b1f2114a339365232bf) |
Alx Sa <cmyk.student@gmail.com> | no | upstream, after 2.0.4 | 2023-01-24 | |
| scripts-move-Predator-script-from-GIMP-main-repository.patch | scripts: move Predator script from GIMP main repository. The Predator script was broken because it relied on the plug-in-max-rgb, which doesn't exist anymore in core GIMP. Rather than adding back the max-rgb plug-in, it was ported and archived in gimp-data-extras (see previous commit), and so is the Predator script. They are funny scripts, but we can't really say they are absolute necessary base scripts for a raster editor. Maybe later we can experiment with both these plug-ins to make them into extensions and ship them again on the future extension platform. In the main repo, this script was in plug-ins/script-fu/scripts/predator.scm See report gimp#5440. (cherry picked from commit e37419279145e052302733f15e6bb7ce44ff47b3) |
Jehan <jehan@girinstud.io> | no | upstream, after 2.0.4 | 2023-01-24 | |
| plug-ins-make-max-rgb-buildable-as-an-external-plug-in.patch | plug-ins: make max-rgb buildable as an external plug-in. Since it's not in the main repo anymore, we can't use the *STD_SET_I18N macros anymore, nor the stdplugins-intl.h header. Disable internationalization for now (though I still include glib/gi18n-lib.h just so that we don't have to remove the _() gettext calls for now; but these will mostly be bogus until we handle proper localization). This file is now easily buildable with command: > gimptool-2.99 max-rgb.c (cherry picked from commit ee95fd2eb684207716cbdafb26ad5c44934dbbce) |
Jehan <jehan@girinstud.io> | no | upstream, after 2.0.4 | 2023-01-26 | |
| Add-obsoleted-scripts-from-gimp-2.99.patch | Add obsoleted scripts from gimp 2.99 gimp 8464 9878 9885 The scripts were not in the menus and not called from the gimp repo. Remotely possible that some third party script wants these. (cherry picked from commit 7430f3b078a0be20ec442c4c40b38d9138d711a4) |
bootchk <konnekerl@gmail.com> | no | upstream, after 2.0.4 | 2023-08-18 |