zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Previous zsh.yo.in patch wasn't good enough
Date: Sun, 5 Dec 1999 17:05:27 +0000	[thread overview]
Message-ID: <991205170527.ZM23739@candle.brasslantern.com> (raw)
In-Reply-To: <991205165636.ZM23631@candle.brasslantern.com>

On Dec 5,  4:56pm, I wrote:
}
} } Then a sed over that generates zsh.texi in the build tree, with the
} } transformed name in the appropriate place.  We run makeinfo on that.
} 
} The easiest way to do this is to get rid of the "%.info: $(tzsh).texi"
} rule and simply have "install.info: $(sdir)/zsh.texi.in".

Two things:

First, of course I mean "install.info: zsh.texi" and have another rule
for generating zsh.texi from zsh.texi.in.

Second, it just occurred to me that having program name transforms apply
to the documentation changes the results of "make targz-doc" from the top
level directory; in fact, without hacking .distfiles during the build,
"make targz-doc" won't work at all with a transformed program name.

Maybe that's OK, as we don't really want someone distributing a tar file
with transformed names in the documentation, but it's a point to note.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-12-05 17:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-02 18:26 Bart Schaefer
1999-12-03  9:10 ` Zefram
1999-12-03 15:16   ` Bart Schaefer
1999-12-03 15:36     ` Clint Adams
1999-12-03 15:39     ` Zefram
1999-12-03 15:48       ` Zefram
1999-12-03 17:09         ` Bart Schaefer
1999-12-05 12:34           ` Zefram
1999-12-05 16:56             ` Bart Schaefer
1999-12-05 17:05               ` Bart Schaefer [this message]
1999-12-06 10:04                 ` Zefram
1999-12-06 10:22               ` Zefram
1999-12-03 15:55       ` Clint Adams
1999-12-03 16:43         ` Bart Schaefer
1999-12-03 16:54           ` Clint Adams

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=991205170527.ZM23739@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).