On 01/17/2017 06:08 AM, Markus Armbruster wrote: > > Three possible solutions, in increasing order of complexity: > > 1. Live with the warning from old versions. If a new version comes > around that does something with @subtitle, it'll just work. > > 2. Suppress the warning with @iftex-hammer. No change in output now. > If a new version comes around that does something with @subtitle, we > won't profit unless we take out the @iftex. > > 3. Replace -D by @set, either by preprocessing .texi, or by including a > generated snippet. No change in output now. If a new version comes > around that does something with @subtitle, it'll just work.
Automake projects use option 3 - they create version.texi with @set commands, then @include that into the main file. Should be fairly easy to crib the makefile magic from an autotooled project if you want to go that option. > > My order of preference is aligned with decreasing complexity, i.e. first > 1., then 2., then 3. I'm fine with any of the options (3 is nicest, but also the most work). I do agree, however, that if we are going to include version information (which I find useful), then we want it in both pdf and html outputs. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
