After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 605552 - Use Argyll tools installed in /usr/local/bin as well
Use Argyll tools installed in /usr/local/bin as well
Status: RESOLVED FIXED
Product: gnome-color-manager
Classification: Core
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-color-manager-maint
gnome-color-manager-maint
Depends on:
Blocks:
 
 
Reported: 2009-12-27 17:19 UTC by Pascal de Bruijn
Modified: 2009-12-28 10:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Also evaluate /usr/local/bin when searching for Argyll tools (prefer) (1.07 KB, patch)
2009-12-27 17:19 UTC, Pascal de Bruijn
none Details | Review
Also evaluate /usr/local/bin when searching for Argyll tools (safe/fallback) (1.15 KB, patch)
2009-12-27 17:20 UTC, Pascal de Bruijn
none Details | Review
Also evaluate /usr/local/bin when searching for Argyll tools (prefer) (fixed) (1.07 KB, patch)
2009-12-27 17:54 UTC, Pascal de Bruijn
committed Details | Review

Description Pascal de Bruijn 2009-12-27 17:19:40 UTC
Created attachment 150461 [details] [review]
Also evaluate /usr/local/bin when searching for Argyll tools (prefer)

Currently GCM searches for Debian modified filenames of the Argyll tools and then looks for the original filenames in /usr/bin. However it's entirely possible for folks to have installed Argyll from a binary tarball (or their own source compile) into /usr/local/bin, and thus GCM should support that.

The question is in what order should we check, there a two options:

- Flexible, preferring /usr/local over everything else. For example a distribution like Fedora or Debian does not provide an up to date copy of Argyll, the user can still untar a binary tarball from argyllcms.com into /usr/local/bin to get the latest and greatest from Argyll. This also does imply, if a user untars a binary tarball from argyllcms.com into /usr/local/bin he'll be "suddenly" using a different version of Argyll, without being explicitly told so, even when the old system copy of Argyll is still present.

- Safe/Fallback, preferring everything else over /usr/local, no risks here, but it's not as flexible.

This is of course a matter of policy.
Comment 1 Pascal de Bruijn 2009-12-27 17:20:50 UTC
Created attachment 150462 [details] [review]
 Also evaluate /usr/local/bin when searching for Argyll tools (safe/fallback)

Here's the safe/fallback version of the patch.
Comment 2 Pascal de Bruijn 2009-12-27 17:54:30 UTC
Created attachment 150465 [details] [review]
Also evaluate /usr/local/bin when searching for Argyll tools (prefer) (fixed)

The previous patch had g_free in the wrong place, because of some sloppy copy-pasting of mine. This patch should have that fixed.
Comment 3 Richard Hughes 2009-12-28 10:24:22 UTC
Review of attachment 150465 [details] [review]:

Looks fine, thanks.