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 628962 - Code contains hardcoded path with /usr/libexec
Code contains hardcoded path with /usr/libexec
Status: RESOLVED FIXED
Product: gnome-packagekit
Classification: Core
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-packagekit-maint
gnome-packagekit-maint
Depends on:
Blocks:
 
 
Reported: 2010-09-07 14:26 UTC by Vincent Untz
Modified: 2010-10-07 14:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Untz 2010-09-07 14:26:29 UTC
static gboolean
gpk_dbus_task_path_is_trusted (const gchar *exec)
{
	/* special case the plugin helper -- it's trusted */
	if (g_strcmp0 (exec, "/usr/libexec/gst-install-plugins-helper") == 0 ||
	    g_strcmp0 (exec, "/usr/libexec/pk-gstreamer-install") == 0)
		return TRUE;
	return FALSE;
}

I understand why this is hardcoded. However, we don't use /usr/libexec in openSUSE. Does it make sense to either change this to $(libexecdir), or to provide a configure switch for this?

I'm willing to write the patch, just tell me what you prefer :-)
Comment 1 Richard Hughes 2010-09-07 15:41:05 UTC
$(libexecdir) -> -DLIBEXECDIR in Makefile.am please. Thanks dude.
Comment 2 Vincent Untz 2010-10-07 14:54:13 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.