Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: Previous zsh.yo.in patch wasn't good enough
- X-seq: zsh-workers 8888
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH: Previous zsh.yo.in patch wasn't good enough
- Date: Fri, 3 Dec 1999 17:09:25 +0000
- In-reply-to: <E11tuwR-0001Gj-00@xxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <E11tuwR-0001Gj-00@xxxxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author