[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [blt] how do you tar a set of files for a package
David Lawyer wrote:
> On Wed, May 03, 2000 at 07:33:57AM -0400, email@example.com wrote:
> > Frequently Executed Commands for a package
> > Frequently Used Flags
> I think this belongs embedded in the command itself. For tar it's
> "tar --help" snip "tar -h" might mean short help (
> This is a small part of the
> big task of integrating Linux documentation and the group that was
> working on this topic fell apart. Most of the man pages are supplied
> with the software and are not done by LDP, but we need to be concerned
> about them.
> -- David Lawyer
The format and presentation of information about a software package is or should
be absolutely separate from the structure of the information itself. If the
information is stored in a "proper" way, the various formats such as -h --help
you suggest would be extractable subsets. So would complete man pages, info
pages, doc-book howtos doc-book manuals parts of faqs and fecs (frequently
executed commands) and any other sort of documentation view you can dream up.
The point is to have documentation sources that can be processed by a program to
produce ANY format of documentation desired. What this format should be is
something that needs work. I don't believe it exists yet.
Is XML a good tool for modeling the structure of data? Is SGML? Is doc-book
the definitive data type definition for documentation? Is Doc-Book future
version 2? future version 3? Who's working on the next steps?
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com