aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2015-09-18 15:29:18 -0400
committerSteven Rostedt <rostedt@goodmis.org>2016-03-22 10:48:53 -0400
commit01b3337df3544cef42be5243a25ed4e005c80efa (patch)
treeb2f1e2c57cfc43f7b4ac85917f93b2f02bebd4dc
parentbdf9ecb7e2b8b22484e94001530607de65b949e8 (diff)
downloadtrace-cmd-01b3337df3544cef42be5243a25ed4e005c80efa.tar.gz
trace-cmd: Always use /var/run and /var/lib
Looking at documentation on the Internet, it seems that even if a tool is installed in /usr/local, it still should be using /var/run and /var/lib, as those are not places that will get overrided by upgrades, but all versions of trace-cmd should know about it. I still keep it dynamic for installing in $HOME, as that may not be done by a administrative user. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-rw-r--r--Makefile8
1 files changed, 1 insertions, 7 deletions
diff --git a/Makefile b/Makefile
index c058adb1..62cb25b6 100644
--- a/Makefile
+++ b/Makefile
@@ -53,12 +53,6 @@ export man_dir man_dir_SQ html_install html_install_SQ INSTALL
export img_install img_install_SQ
export DESTDIR DESTDIR_SQ
-ifeq ($(prefix),/usr)
-root = /
-else
-root = $(prefix)/
-endif
-
ifeq ($(prefix),$(HOME))
plugin_dir = $(HOME)/.trace-cmd/plugins
python_dir = $(HOME)/.trace-cmd/python
@@ -70,7 +64,7 @@ PLUGIN_DIR = -DPLUGIN_DIR="$(plugin_dir)"
PYTHON_DIR = -DPYTHON_DIR="$(python_dir)"
PLUGIN_DIR_SQ = '$(subst ','\'',$(PLUGIN_DIR))'
PYTHON_DIR_SQ = '$(subst ','\'',$(PYTHON_DIR))'
-var_dir = $(root)var
+var_dir = /var
endif
VAR_DIR = -DVAR_DIR="$(var_dir)"