Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 13282 [details] the ebuild
worked for me, but both gimp-freetype 0.2 and 0.3 should be slotted.
sorry, installation seems to be wrong : the plugin was installed in /usr/lib/gimp/1.2 dir, not /usr/lib/gimp/1.3 : >>> Merging media-gfx/gimp-freetype-0.3 to / --- /usr/ --- /usr/lib/ --- /usr/lib/gimp/ --- /usr/lib/gimp/1.2/ --- /usr/lib/gimp/1.2/plug-ins/ >>> /usr/lib/gimp/1.2/plug-ins/freetype --- /usr/share/ --- /usr/share/doc/ >>> /usr/share/doc/gimp-freetype-0.3/ etc...
in fact, the local GIMP_PLUGIN_DIR=`gimptool --gimpplugindir` has used the gimp-1.2 gimptool, while the gimp-1.3 didn't install a gimptool. so when i unmerged gimp-1.2, no gimptool was available, which could have lead to install the plugin in /plug-ins/ instead of /usr/lib/gimp/1.3/plug-ins/. you should use "/usr/bin/gimptool-1.3" instead of just "gimptool". no symlinks were created at my gimp-1.3.17 merge, nor for "gimp" neither for "gimptool".
effectively, no "dosym" in the gimp-1.3.17 ebuild. either the gimp-freetype have to be modified to use gimptool-1.3, or the gimp-1.3* ebuilds have to be changed to create symlinks for gimp and gimptool.
Yes, the problem with missing symlinks is a bit older. See #22840 e.g.. Since gimp-1.2* ist still the stable version, gimp-print is not compatible with gimp-1.3* and the versions in both slots make use of this symlinks, I'm not sure if it will be fixed. I added this bug on 06-14, ask yourself why it is not in portage allready.
because we have a _lot_ of work todo and few people to do it. A plugin for a unstable p.mask-ed version of a package is not a priority to me. And this build should be adapted to use gimp(tool)-1.3 directly.
>because we have a _lot_ of work todo and few people to do it. A plugin for a unstable p.mask-ed version of a package is not a priority to me. Yes, meant nothing else. Sounded my comment offending? It shouldn't.
I can understand it is annoying and frustrating to see a bug linger on this long with little work being done on it and i don't blame you for that, i just want to make clear why it is that way and hope you'll find that acceptable. Doesn't mean you can't go on and test and refine the ebuild that is here, as was happening the last day.
Created attachment 15851 [details] new ebuild the gimp-freetype-0.3 ebuild that use gimptool-1.3 instead of gimptool, and is on slot 1 (gimp-freetype-0.2 is on slot 0).
i don't think this ebuild is needed anymore, since gimp-2's font tool is using freetype2.
'right
