public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Peter Teoh" <htmldeveloper@gmail.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Start of Systemtap Tapset Reference manual
Date: Mon, 17 Nov 2008 06:00:00 -0000	[thread overview]
Message-ID: <804dabb00811162159m289a403ck18603b4fceb793e0@mail.gmail.com> (raw)
In-Reply-To: <4919B665.2060606@redhat.com>

(resent due to bounced email)

Not sure if my suggestion has any relevancy or unanticipated or not,
but I will just describe it.

what i am proposing is:   do the minimal work to create the
documentation, maximize the consistency with that of Linux Kernel, so
that UNIFICATION of systemtap with Linux Kernel source may one be
possible.

How?

a.   When create the documentation, for example, the current
systemtap/doc always assumed that the entire subdirectory can be moved
to become Linux Kernel's Documentation's subdirectory, perhaps
"systemtap" as the name.

b.   So when a user go to Linux Kernel source and enter "make
htmldocs", or "make pdfdocs", a htmlized or pdf-ized document will be
created under DocBook.  Ie, there will be ZERO scripting effort from
systemtap developer, and all existing infrastructure provided by Linux
Kernel source's "script" subdirectory can be reused.

On a wider scale, the above can be generalized further.   But I would
like some feedback before venturing too far.


On Wed, Nov 12, 2008 at 12:44 AM, William Cohen <wcohen@redhat.com> wrote:
>
> Hi all,
>
> The infrastructure is in place to extract xml from the files in systemtap/tapset for the reference manual. I have taken the documentation from the timestamp functions and placed it in the timestamp.stp file. The xml in the timestamp.stp file is preceded by ///.
>
> The process of generating the document is fairly simple. Go to the systemtap/doc/SystemTap_Tapset_Reference. If there have been changes to the tapset files, the xml can extracted from the tapset files with:
>
> make extract-xml
>
> You will need to have publican installed on the computer to build the pdf or html files. There are instructions on publican at:
>
> http://sourceware.org/systemtap/wiki/PublicanQuikHowto
>
> Once publican is installed make the pdf with:
>
> make pdf-en-US
>
> Or if HTML is desired:
>
> make html-en-US
>
> The resulting output will be in placed in the appropriate directory:
>
> systemtap/doc/SystemTap_Tapset_Reference/tmp/pdf
> systemtap/doc/SystemTap_Tapset_Reference/tmp/html
>
> I have attached the current Tapset_Reference.pdf to get feedback on this process  and refine it, so I don't have to revise a bunch of entries.
>
> -Will



--
Regards,
Peter Teoh

  parent reply	other threads:[~2008-11-17  6:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 16:45 William Cohen
     [not found] ` <491CBA1C.4080108@redhat.com>
2008-11-14 14:08   ` William Cohen
2008-11-17  6:00 ` Peter Teoh [this message]
     [not found] ` <804dabb00811162156s7cc931deja89861e47571331f@mail.gmail.com>
2008-11-18 16:55   ` William Cohen
2008-11-18 20:44     ` Randy Dunlap
2008-11-19  1:01       ` Peter Teoh
2008-11-19 16:33       ` William Cohen
2008-11-20 21:31       ` William Cohen
2008-11-20 21:41         ` Randy Dunlap
2008-11-21 14:54           ` William Cohen
2008-11-21 23:00           ` Tweaks for kernel-doc to parse systemtap tapsets William Cohen
2008-11-24 16:48           ` Start of Systemtap Tapset Reference manual William Cohen
2008-11-24 19:16             ` William Cohen
2008-11-25 11:27               ` Mark Wielaard
2008-11-25 15:04                 ` William Cohen
2008-11-27  1:47                   ` Peter Teoh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=804dabb00811162159m289a403ck18603b4fceb793e0@mail.gmail.com \
    --to=htmldeveloper@gmail.com \
    --cc=systemtap@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).