gimp is a symlink to gimp-2.2 gimp-remote is a symlink to gimp-remote-2.2 Why there is not gimptool symlink? $ ls -l /usr/bin/gimp* lrwxrwxrwx 1 root root 8 Dec 30 15:54 /usr/bin/gimp -> gimp-2.2* -rwxr-xr-x 1 root root 3.1M Dec 30 15:53 /usr/bin/gimp-2.2* lrwxrwxrwx 1 root root 15 Dec 30 15:53 /usr/bin/gimp-remote -> gimp-remote-2.2* -rwxr-xr-x 1 root root 12K Dec 30 15:53 /usr/bin/gimp-remote-2.2* -rwxr-xr-x 1 root root 1.5K Dec 30 14:19 /usr/bin/gimpprint-config* -rwxr-xr-x 1 root root 11K Dec 30 15:53 /usr/bin/gimptool-2.0* $ eix ^gimp\$ * media-gfx/gimp Available versions: 1.2.5 2.2.6-r1 2.2.8-r1 ~2.2.9 ~2.2.10 *9999 Installed: 2.2.8-r1 I've looked the ebuilds (2.2.8-r1, 2.2.9 and 2.2.10), and I see in all of them: src_install() { [...] # Create the gimp-remote link, see bug #36648 dosym gimp-remote-2.2 /usr/bin/gimp-remote } pkg_postinst() { alternatives_auto_makesym "/usr/bin/gimp" "/usr/bin/gimp-[0-9].[0-9]" [...] } Couldn't all three symlinks be created the same way? I mean... why not use "alternatives_auto_makesym" for all three symlinks? Or use "dosym" for all of them. I don't know how "alternatives_auto_makesym" work, but I would like to remember that gimp-1.2.5 is still available, and is slotted. What would be better? If the link exists, update it, or let the first (or last) package to be installed set it? I prefer to update it to latest version, and I *hope* "alternatives_auto_makesym" do that (I did not read documentation about it). Related bugs: bug 810 - gimp-1.2.3 ebuild doesn't install a symlink to gimptool bug 36648 - Missing gimp-remote in media-gfx/gimp
This is already fixed in media-gfx/gimp-9999. Allanonjl, will you backport it to gimp-2.2.11* (or should I)?
I just discussed this with upstream in #gimp on GIMPNet: 21:33:55 < brix> would it be incorrect to install a "gimptool -> gimptool-2.0" symlink distribution wise? 21:39:21 < mitch> brix: um, don't we do that already? 21:40:27 < mitch> oh well no 21:41:09 < brix> mitch: I seem to recall something about plug-ins should not use "gimptool" - they should call the version of gimptool they support 21:41:44 * brix is preparing gentoo for gimp-2.4 21:42:46 < mitch> yes they should call gimptool-2.0 21:43:25 < brix> so a symlink shouldn't be installed? 21:43:30 < mitch> nope 21:43:33 < brix> ok, thanks I have therefore corrected gimp-9999.ebuild to not install the symlink, no backport needed. Closing this as INVALID (but it was a good question :)
Just a little comment: gimp and gimp-remote symlinks were being created by different ways (in 2.2.x ebuilds). One was using "dosym", and the other "alternatives_auto_makesym". Would not be prefered if both were created the same way? Has this been fixed? (looking at 2.2.8-r1 ebuild, it was not fixed; though it was ok on 9999 ebuild)
(In reply to comment #3) > Has this been fixed? (looking at 2.2.8-r1 ebuild, it was not fixed; though it > was ok on 9999 ebuild) Yeah, but it's not critical.
