Opened 7 years ago
Closed 7 years ago
#10711 closed enhancement (fixed)
gimp-2.10.0
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | 8.3 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
Michael Natterer has now announced this:
Hi,
After 6 years of development...
We just released GIMP 2.10.0 \o/
This is the first release of the new stable 2.10 series.
For a complete list of changes since 2.10.0-RC2 please see the "Changes" section below.
There is also a release announcement on www.gimp.org:
https://www.gimp.org/news/2018/04/27/gimp-2-10-0-released/
Detailed release notes for 2.10, including many screenshots and videos of new features, can be found here:
https://www.gimp.org/release-notes/gimp-2.10.html
Also, we're going to have some beers now...
Happy GIMPing, --Mitch
Based on the two RC releases, libmypaint and libmypaint-brushes are required. The help for 2.10 has not yet been released, and when I last looked at the git version of help it appeared to not yet be complete (I tried to get help for something, probably the new shadows/highlights filter under 'colour') and it reported an error).
More significantly, two issues have so far been reported:
- libmypaint-1.3.0 requires gegl-0.3 but gimp now requires gegl-0.4.
- a report that gimp.pc.in still contains a reference to gegl-0.3, and that this prevents packages such as g'mic (not in the book, but important for photographers) from building.
I'll keep an eye on this.
Meanwhile, I guess I should also note the following:
- user files now go into ~/.config/GIMP/2.10 instead of ~/gimp-2.8 (this affects your own scripts/plugins if you need to install them as a user, or edit/debug scripts).
- some existing scripts which gave popup warnings in recent 2.9 are fine in the RCs, others which worked in 2.9.6 will need changes (I had one of each).
- working on images is fastest if they are either 8-bit or else 32-bit-floating-point (the new 'precision' option allows conversion) - and pngs from a 32-bit fp image will now be exported as 16-bit.
With the exception of the issues which have been reported, this all sounds good.
Change History (8)
comment:1 by , 7 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
follow-ups: 4 5 comment:2 by , 7 years ago
comment:3 by , 7 years ago
Meanwhile, a question whether the fix for gimp.pc.in could be added for the official 2_20_0 tag got the response:
it will however be fixed in 2.10.2 - to be expected along with another GEGL release in the next handful of days
comment:4 by , 7 years ago
Replying to ken@…:
Replying to ken@…:
- libmypaint-1.3.0 requires gegl-0.3 but gimp now requires gegl-0.4.
Well, that was what was reported on the list, but my download of libmypaint-1.3.0 only uses gegl if it is specifically enabled. Looking at google, it appears that libmypaint-gegl was needed in 2015, but it is NOT needed now.
comment:5 by , 7 years ago
Replying to ken@…:
For gimp.pc.in, now fixed in git :
diff --git a/configure.ac b/configure.ac index 33754e3..e28a55e 100644 --- a/configure.ac +++ b/configure.ac @@ -174,6 +174,7 @@ AC_SUBST(GTK_REQUIRED_VERSION) AC_SUBST(GTK_WIN32_RECOMMENDED_VERSION) AC_SUBST(CAIRO_REQUIRED_VERSION) AC_SUBST(CAIRO_PDF_REQUIRED_VERSION) +AC_SUBST(GEGL_MAJOR_MINOR_VERSION) AC_SUBST(GEGL_REQUIRED_VERSION) AC_SUBST(GEXIV2_REQUIRED_VERSION) AC_SUBST(LCMS_REQUIRED_VERSION)I'm sure we can do that with a sed, (and autoreconf, of course).
Except that isn't the whole fix. A simpler complete fix for 2.10.0 is sed -i 's/gegl-0.3/gegl-0.4/' gimp.pc.in
g'mic-2.2.3 pre (with gmic-qt-v.2.2.2) now builds and installs - there was a report during the week about gmic needing to be the unmaintained gtk build. Unfortunately, my preferred raw plugin is no-longer working.
For gimp-help, the online help appears to be present, but requires gvfs.
follow-up: 7 comment:6 by , 7 years ago
I built gvfs (with a minimum of its dependencies), rebuilt gimp, and based on past experience I then added yelp - and thus webkitgtk. Online help now works, but to my surprise it opens in my normal browser (firefox). So, I'm not sure exactly what is needed at _runtime_ for this.
But for the book, I'll leave it a little while (there were non-18n changes to gimp-help on Saturday) and then take a fresh tree from git.
comment:7 by , 7 years ago
Replying to ken@…:
I built gvfs (with a minimum of its dependencies), rebuilt gimp, and based on past experience I then added yelp - and thus webkitgtk. Online help now works, but to my surprise it opens in my normal browser (firefox). So, I'm not sure exactly what is needed at _runtime_ for this.
Probably just setting a default browser (it was the fact that the external help pointed to an xml file when gvfs was not installed that confused me). I see that I have
ken@origin ~ $xdg-mime query default x-scheme-handler/http userapp-Firefox-G6HKGZ.desktop
... getting there, but slowly
Replying to ken@…:
For libmypaint, its developers are now mostly working on v2. But libmypaint-gegl is not used in any way by GIMP, so build with --disable-gegl.
For gimp.pc.in, now fixed in git :
I'm sure we can do that with a sed, (and autoreconf, of course).
For gimp-help, in git the blend-tool and one translation have been updated, hopefully a release will soon appear.
I'll give the help a few more days.