repo-remove and repo-elephant don't care whether repo-add.sh.in is updated... but they do require the repo-add target to be up to date, so use that instead. As a bonus, use the same rule for both of them. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> --- New patch, which obsoletes and partially includes: https://lists.archlinux.org/pipermail/pacman-dev/2018-November/022918.html scripts/Makefile.am | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/scripts/Makefile.am b/scripts/Makefile.am index c6b6220e..600c405b 100644 --- a/scripts/Makefile.am +++ b/scripts/Makefile.am @@ -211,13 +211,9 @@ pkgdelta: $(srcdir)/pkgdelta.sh.in repo-add: $(srcdir)/repo-add.sh.in -repo-remove: $(srcdir)/repo-add.sh.in - $(AM_V_at)$(RM) repo-remove - $(AM_V_at)$(LN_S) repo-add repo-remove - -repo-elephant: $(srcdir)/repo-add.sh.in - $(AM_V_at)$(RM) repo-elephant - $(AM_V_at)$(LN_S) repo-add repo-elephant +repo-remove repo-elephant: repo-add + $(AM_V_at)$(RM) $@ + $(AM_V_at)$(LN_S) repo-add $@ .SECONDEXPANSION: $(WRAPPER): \ -- 2.19.1