zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: schaefer@candle.brasslantern.com (Bart Schaefer)
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Previous zsh.yo.in patch wasn't good enough
Date: Fri, 3 Dec 1999 15:39:13 +0000 (GMT)	[thread overview]
Message-ID: <E11tuni-00019k-00@crucigera.fysh.org> (raw)
In-Reply-To: <991203151631.ZM18044@candle.brasslantern.com> from Bart Schaefer at "Dec 3, 1999  3:16:31 pm"

Bart Schaefer wrote:
>The source tree is already modified during building; all the *.1 files go
>in $(sdir)/Doc when the man pages are generated, Etc/FAQ and META-FAQ are
>written to the source tree, etc.

But they don't get modified during a normal build after unpacking the
source -- those files are already up to date in the source tree, and so
don't get rebuilt.  They do get automatically rebuilt if their source
files change, in which case the source tree has already been modified.

The source tree should not be modified by the build process alone;
building should only modify the source tree if the source has already
been modified.

>If you're asking whether we should get rid of zsh.yo.in again so that
>zsh.yo is not a generated file, you'll have to ask Clint.  I'm just
>cleaning up after his patches in 8827 and 8841.

Yes, I think we should be able to do that.

-zefram


  parent reply	other threads:[~1999-12-03 15:39 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 [this message]
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
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=E11tuni-00019k-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=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).