From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: PATCH: Doc/Makefile.in missing $(DESTDIR)
Date: Wed, 29 Sep 1999 23:05:08 +0100 [thread overview]
Message-ID: <19990929230508.A15123@thelonious.new.ox.ac.uk> (raw)
Index: Doc/Makefile.in
===================================================================
RCS file: /usr/local/cvsroot/zsh/Doc/Makefile.in,v
retrieving revision 1.3
diff -u -r1.3 Makefile.in
--- Doc/Makefile.in 1999/09/29 19:29:50 1.3
+++ Doc/Makefile.in 1999/09/29 21:57:08
@@ -186,7 +186,7 @@
fi || exit 1; \
done
if $(SHELL) -c 'install-info --version' >/dev/null 2>&1; then \
- install-info --dir-file=$(infodir)/dir $(infodir)/zsh.info; \
+ install-info --dir-file=$(DESTDIR)$(infodir)/dir $(DESTDIR)$(infodir)/zsh.info; \
else true; fi
install.html: zsh_toc.html
reply other threads:[~1999-09-30 2:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990929230508.A15123@thelonious.new.ox.ac.uk \
--to=adam@thelonious.new.ox.ac.uk \
--cc=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).