bug#54063: automake cannot run without generated Texinfo manual
On Thu, Feb 24, 2022 at 10:32:20PM -0500, Mike Frysinger wrote: > > The only issue I see is if after the > > file is generated the @setfilename is not the same as the file base name > > there will be errors. I do not think that automake should support that > > setup, but maybe it would be good to state it in the documentation. > > Maybe something like: > > > > "Texinfo files that are generated should have a basename matching > > @setfilename, if there is a @setfilename." > > sounds reasonable, but i don't think this is a new issue. It is not new, sure, but before this change Texinfo generated file were most probably uncommon, and could be much more common and therefore there could be more risk for that kind of mismatch now. Non generated files can have a basename not matching with the @setfilename without that being a problem, I think (though I did not test...). -- Pat
bug#54063: automake cannot run without generated Texinfo manual
Adding a note to the manual is fine, but what would be (much) more likely to actually get noticed by users is a runtime warning. What is the actual behavior when the basename and @setfilename don't match? Sorry to be clueless ...
bug#54063: automake cannot run without generated Texinfo manual
On Fri, Feb 25, 2022 at 04:06:34PM -0700, Karl Berry wrote: > Adding a note to the manual is fine, but what would be (much) more > likely to actually get noticed by users is a runtime warning. What is > the actual behavior when the basename and @setfilename don't match? > Sorry to be clueless ... Runtime warning in texi2any or automake? I experienced this issue with automake one time, not on purpose. I don't quite remember well, but my recalling is that the output file was always rebuilt as automake had determined the output file name and the rules when run previously using the basename, while the files where created using the @setfilename by makeinfo. -- Pat
bug#54063: automake cannot run without generated Texinfo manual
Runtime warning in texi2any or automake? Both?
bug#54063: automake cannot run without generated Texinfo manual
On Fri, Feb 25, 2022 at 04:29:11PM -0700, Karl Berry wrote: > Runtime warning in texi2any or automake? > > Both? It seemed to me that @setfilename in texi2any was actually a way to have an output file name different from the input file name. If this is not really useful, we should simply ignore @setfilename in texi2any rather than have a runtime warning. We actually use @setfilename in the test suite to be able to set a file name for a Texinfo string read from a source file and not from an actual file. But there are other ways to specify the file name. -- Pat
bug#54063: automake cannot run without generated Texinfo manual
On 25 Feb 2022 16:06, Karl Berry wrote: > Adding a note to the manual is fine, but what would be (much) more > likely to actually get noticed by users is a runtime warning. What is > the actual behavior when the basename and @setfilename don't match? i don't think it's possible to detect from automake, at least at `automake` time. the point of Patrice's report is that the sources don't exist when automake runs, so it's not possible to inspect them. trying to go further (having automake attempt to trace partial makefile? have it generate a check that runs on the user's system at `make` time?) feels like it's intruding on the territory of texinfo for no real gain. -mike signature.asc Description: PGP signature
