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: Fri, 3 Dec 1999 17:09:25 +0000	[thread overview]
Message-ID: <991203170925.ZM18217@candle.brasslantern.com> (raw)
In-Reply-To: <E11tuwR-0001Gj-00@crucigera.fysh.org>

On Dec 3,  3:48pm, Zefram wrote:
} Subject: Re: PATCH: Previous zsh.yo.in patch wasn't good enough
}
} Zefram wrote:
} >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.
} 
} Which I forgot to explain: if you are doing multiple builds from a single
} source tree, there MUST NOT be any build-specific data in the source tree,
} otherwise the builds will interfere with each other.

My thought (which I now see to have been half-formed) was that the docs
were architecture-independent and hence the same for all builds -- but
of course it's possible to have two build trees with different name
transforms.

This leads me to conclude that the $(tzsh).info change is either going
too far, or not far enough:  If we're renaming zsh.info, why aren't we
renaming zsh.1 and zshall.1 and zshbuiltins.1 etc?  And if we're going
to rename those, then they have to be written to the build tree and not
to the source tree, as well.

I *think* -- based on looking at automake-generated Makefile.in files --
that program name transforms are intended strictly as an install-time
thing, and should not affect compile-time file generation.  Its too bad
that info format requires the files to reference their own names.

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


  reply	other threads:[~1999-12-03 17:09 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 [this message]
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=991203170925.ZM18217@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).