Since commit b5d62d2c91a2caf5c18945921cdf12af6f36b2d4, all scripts depend on libmakepkg, not just makepkg itself. Additionally, 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. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> --- scripts/Makefile.am | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/scripts/Makefile.am b/scripts/Makefile.am index c6b6220e..83d53a51 100644 --- a/scripts/Makefile.am +++ b/scripts/Makefile.am @@ -203,19 +203,19 @@ makepkg-template: \ $(AM_V_GEN)$(edit) $< > $@ $(AM_V_at)chmod +x,a-w $@ -pacman-db-upgrade: $(srcdir)/pacman-db-upgrade.sh.in +pacman-db-upgrade: $(srcdir)/pacman-db-upgrade.sh.in $(LIBMAKEPKG_IN) -pacman-key: $(srcdir)/pacman-key.sh.in +pacman-key: $(srcdir)/pacman-key.sh.in $(LIBMAKEPKG_IN) -pkgdelta: $(srcdir)/pkgdelta.sh.in +pkgdelta: $(srcdir)/pkgdelta.sh.in $(LIBMAKEPKG_IN) -repo-add: $(srcdir)/repo-add.sh.in +repo-add: $(srcdir)/repo-add.sh.in $(LIBMAKEPKG_IN) -repo-remove: $(srcdir)/repo-add.sh.in +repo-remove: repo-add $(AM_V_at)$(RM) repo-remove $(AM_V_at)$(LN_S) repo-add repo-remove -repo-elephant: $(srcdir)/repo-add.sh.in +repo-elephant: repo-add $(AM_V_at)$(RM) repo-elephant $(AM_V_at)$(LN_S) repo-add repo-elephant -- 2.19.1