bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building SVN source failures: VPATH builds; Cygwin


From: Hans-Bernhard Bröker
Subject: Re: Building SVN source failures: VPATH builds; Cygwin
Date: Fri, 13 Jan 2017 23:53:12 +0100
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0

Am 13.01.2017 um 20:56 schrieb Gavin Smith:=

I've removed many of the files you recommended. I haven't removed
texinfo.awk yet, I need to work out what to do with it first.

As long as you keep it, you'll have to add something to man/Makefile.am or texindex/Makefile.am that makes sure that either

a) makes a copy of texindex.awk into $(top_builddir)/texindex so './texindex' can be called from there, or

b) texindex/Makefile.am builds texindex.awk into $(srcdir) like info files are, or

c) man/Makefile.am sets TEXINDEX_AWK to run it

The key drawback of option c) would be that if somebody with a VPATH build setup changes ti.twjr, they'll still be running the outdated $(srcdir)/texindex.awk for this step, instead of the fresh $(builddir) version.

> I think
another solution could be to check in the man pages to version
control, but I haven't looked at this detail.

That would run into the same kind of problem as option c): the risk of having stale files used without any apparent symptom of that having happened.

I usually prefer sticking with the "no generated files in version control (except for rather exotic generators)" approach. The next best one is "keep version control contents identical to the distribution tarball," assuming version control can be trusted with the time stamps. You're currently working a mixture of the two. I can't see much of a benefit in that.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]