On 19/04/2014 17:23, Joe Taylor wrote: Hi Joe, > Hi all, > >>> If we need one for each executable, would should probably take inventory >>> of all aps and maybe make one Manpage or set of pages for all ? as allot >>> of it overlaps >> I agree. I thought, a single man page that covered everything and have >> other pages shadow that one, so for example for jt9: >> >> file man1/jt9.1: >> .so man1/wsjtx.1 >> >> would be sufficient and I can generate that internally. Then >> man1/wsjtx.1 can have all the details of everything. This is traditional >> for linked utilities, grep(1) is a classic example. > Except we don't have a program called jt9. Guess you mean wsjt? The > full suite (in order of their birth years) is WSJT, MAP65, WSPR, WSJT-X, > and WSPR-X. We do in terms of Linux packaging. Technically any executable that is bundled into a package should have a man page and that is policed by the package checking tools like 'lintian' which would be used by distribution repository guardians to check validity of new packages being submitted.
Either way I hope it will become moot sometime in the near future. > > -- Joe 73 Bill G4WJS. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
