Steve McIntyre wrote: > On Thu, Jun 16, 2011 at 02:04:34PM -0400, Michael Stone wrote: >>On Thu, Jun 16, 2011 at 06:50:21PM +0100, Steve McIntyre wrote: >>>For now, the attached debdiff simply disables generation of the docs >>>for cross-builds. The right answer (IMHO) would be to convince >>>upstream to generate their docs in a more sane way (e.g. having a >>>common source for help information that could be used both for --help >>>output *and* the man pages). >> >>They don't strictly need to be built at build time, but the >>alternative does make things a bit more complicated. Basically, any >>time a patch changes the help you need to rebuild it, but that could >>be done at packaging time with some kind of option to apply all the >>patches, build & generate the man pages, save a diff of the new man >>pages, and add that diff to the package. Patches welcome. :-) > > :-) > >>I'll actually look closer at it tonight, there may even be a simpler >>solution than that as I usually try really hard to avoid touching the >>help output (because it also screws up localization strings) and it >>might be sufficient to try to just keep the versions from the >>upstream tar. > > Hmmm, OK. Is there no chance of persuading upstream to do things > better and either just ship man pages (yeah, I know about the GNU info > thing, ick!) or to split out the help text into separate data files > that could then be transformed/compiled into both man pages and the > binaries?
Upstream tarballs already include the generated man pages: $ tar tf coreutils-8.12.87-23dd.tar.xz|grep '.1$'|wc -l 124 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
