[Privoxy-commits] [privoxy] 01/09: Rename slackware/rc.privoxy.orig to slackware/rc.privoxy.in

[User Git]

This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch master
in repository privoxy.

commit f8f5eed67547f87a9ed3da9f83520b56c4a5952a
Author: Fabian Keil <fk at fabiankeil.de>
AuthorDate: Mon Jan 18 16:01:59 2021 +0100

    Rename slackware/rc.privoxy.orig to slackware/rc.privoxy.in
    
    ... as suggested by Roland. This shold silence complaints
    when building Debian packages and hopefully still works
    on Slackware ...
---
 GNUmakefile.in                               | 4 ++--
 slackware/{rc.privoxy.orig => rc.privoxy.in} | 0
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/GNUmakefile.in b/GNUmakefile.in
index 2abf75d7..bd350353 100644
--- a/GNUmakefile.in
+++ b/GNUmakefile.in
@@ -785,7 +785,7 @@ clean:
 	$(RM) a.out $(OBJS) $(W32_FILES) $(W32_INIS) $(PROGRAM) default.action \
 		config.base config.tmp \
 		`find . \( -name TAGS -o -name tags \) -a -not -path "./.git/*"` \
-		`find . -name "*.orig" -a -not -name rc.privoxy.orig -a -not -path "./.git/*"`
+		`find . -name "*.orig" -a -not -path "./.git/*"`
 
 clean-editor-files:
 	$(RM) `find . -name "*~"`
@@ -994,7 +994,7 @@ install: CONF_DEST LOG_DEST PID_DEST check_doc GROUP_T
 	$(CHMOD) $(RWD_MODE) $(DESTDIR)$(LOG_DEST)/logfile || exit 1 ;\
 	if [ "$(prefix)" = "/usr/local" ] || [ "$(prefix)" = "/usr" ]; then \
 		if [ -f /etc/slackware-version ] && [ -d /etc/rc.d/ ] && [ -w /etc/rc.d/ ] ; then \
-               $(SED) 's+%PROGRAM%+$(PROGRAM)+' slackware/rc.privoxy.orig | \
+               $(SED) 's+%PROGRAM%+$(PROGRAM)+' slackware/rc.privoxy.in | \
                $(SED) 's+%SBIN_DEST%+$(SBIN_DEST)+' | \
                $(SED) 's+%CONF_DEST%+$(CONF_DEST)+' | \
                $(SED) 's+%USER%+$(USER)+' | \
diff --git a/slackware/rc.privoxy.orig b/slackware/rc.privoxy.in
similarity index 100%
rename from slackware/rc.privoxy.orig
rename to slackware/rc.privoxy.in

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.