From: Chris Wright <hidden> Date: 2016-06-15 22:42:06
* John W. Linville (linville@tuxdriver.com) wrote:
quoted
Sorry, I absolutely detest other peoples' Makefiles that has
this target. Why would anybody want this?
Is this a serious question? To uninstall the binaries e.g. if you
installed them in the wrong place?
Of course package manager will do better at this, but it is useful to be
able to uninstall. However, I don't think Martin's external script with
all the filenames hardcoded is the right approach. There are $(PROG)
and $(SCRIPTS) which already know all these filenames.
thanks,
-chris
From: John W. Linville <hidden> Date: 2016-06-15 22:42:06
On Fri, Sep 16, 2005 at 11:08:10AM -0700, Chris Wright wrote:
Of course package manager will do better at this, but it is useful to be
able to uninstall. However, I don't think Martin's external script with
all the filenames hardcoded is the right approach. There are $(PROG)
and $(SCRIPTS) which already know all these filenames.
I would agree with that. Definitely better to use the same Makefile
vars used for install to do the uninstall.
John
--
John W. Linville
linville@tuxdriver.com
From: Martin Atukunda <hidden> Date: 2016-06-15 22:42:06
On Fri, Sep 16, 2005 at 11:08:10AM -0700, Chris Wright wrote:
* John W. Linville (linville@tuxdriver.com) wrote:
quoted
quoted
Sorry, I absolutely detest other peoples' Makefiles that has
this target. Why would anybody want this?
Is this a serious question? To uninstall the binaries e.g. if you
installed them in the wrong place?
Of course package manager will do better at this, but it is useful to be
able to uninstall. However, I don't think Martin's external script with
all the filenames hardcoded is the right approach. There are $(PROG)
and $(SCRIPTS) which already know all these filenames.
The external script only removes the symlinks created by ./cmd-rename.sh
- Martin -