when I try to calibrate my screen using GNOME3 standart tools (gnome-control-centre color, gnome-color-manager, argyllcms), I can't do it, because of filename changing: argyllcms ebuild renames all binaries from the package prefixing it with "argyll-", which makes them impossible to use by gnome.
Thanks for reporting. I see that our gnome-color-manager tries to launch "dispcal" instead of "argyll-dispcal". Are there any other argyllcms executables that gnome-color-manager calls incorrectly?
That I don't know, but I suppose that all of them. As I installed argyllcms from local overlay anyway, I just removed this prefixes from ebuild. I didn't try to launch calibration renaming agryll binaries one at a time.
Fixed, thanks for reporting. >*gnome-color-manager-3.2.2-r1 (07 Mar 2012) > > 07 Mar 2012; Alexandre Rostovtsev <tetromino@gentoo.org> > -gnome-color-manager-3.2.1.ebuild, +gnome-color-manager-3.2.2-r1.ebuild, > +files/gnome-color-manager-3.2.2-argyll-prefix.patch: > Use the correct name for Gentoo's argyll-dispcal; add a pkg_postinst message > about argyllcms (bug #407319, thanks to Morse). Drop old.
Created attachment 304741 [details, diff] patch for gnome-color-manager
Not quite fixed yet. g-c-m calls for dispcal in three different places.
Created attachment 304893 [details, diff] upstreamable patch Please test this patch; I believe it should also work on all distros, and would therefore be acceptable for inclusion in gnome-color-manager upstream.
You need a patch for your patch :) line 26: - if (!command == NULL) + if (command == NULL) Othen that that - yes, it's working. good to go to upstream.
(In reply to comment #7) Thanks! Updated the patch in portage and submitted upstream at https://bugzilla.gnome.org/show_bug.cgi?id=672028 >*gnome-color-manager-3.2.2-r2 (14 Mar 2012) > > 14 Mar 2012; Alexandre Rostovtsev <tetromino@gentoo.org> > -gnome-color-manager-3.2.2-r1.ebuild, +gnome-color-manager-3.2.2-r2.ebuild, > files/gnome-color-manager-3.2.2-argyll-prefix.patch: > Fix the argyll-dispcal patch so it works properly (bug #407319).