From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23044 invoked from network); 6 Dec 1999 10:04:31 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Dec 1999 10:04:31 -0000 Received: (qmail 19693 invoked by alias); 6 Dec 1999 10:04:24 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8907 Received: (qmail 19686 invoked from network); 6 Dec 1999 10:04:23 -0000 Subject: Re: PATCH: Previous zsh.yo.in patch wasn't good enough In-Reply-To: <991205170527.ZM23739@candle.brasslantern.com> from Bart Schaefer at "Dec 5, 1999 5: 5:27 pm" To: schaefer@candle.brasslantern.com (Bart Schaefer) Date: Mon, 6 Dec 1999 10:04:19 +0000 (GMT) Cc: zsh-workers@sunsite.auc.dk X-Mailer: ELM [version 2.4ME+ PL48 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Zefram Bart Schaefer wrote: >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. This is a good, but not conclusive, argument against doing name transformations for the documentation: we want the documentation tarball to be build-independent. OTOH, we can reasonably assume that developers will not use a transformed name to build it. We should build all documentation using the untransformed name. This makes the files that go into -doc.tar.gz. The only exception to this is the info files, which need to be rebuilt if the name changes. I think we can reasonably distribute zsh.texi as we used to, with zsh.info(|-<->) in -doc.tar.gz, and then have an extra rule that if building with a transformed name, then the info files *also* get built with the transformed name, and it is those info files that get installed. -zefram