This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Start of Systemtap Tapset Reference manual
- From: "Peter Teoh" <htmldeveloper at gmail dot com>
- To: SystemTAP <systemtap at sources dot redhat dot com>
- Date: Mon, 17 Nov 2008 13:59:55 +0800
- Subject: Re: Start of Systemtap Tapset Reference manual
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=bgOPwnoTpk1ERoWgEv4krg3dpwae9gOQ65c3Bgwafsc=; b=GP63zoF7pwsTeM78IpSS75ZDhLMoCHIROQpEfw9MSrymn/ZMFdtLORLIyTNpdSL0sw eU+pfZ8g+ifO1sjw+hLr/p8a1cGVgy5y2PU+tRuqJ25nn/zlBJPRi1eaApc7imltStzI bKRG5C++v0u1ZLhABhUKW0XRmr/Sq0DEm9MkM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CSU9Z8PpbJgDGc2Y3aoJfhriubnMd4sIG5KkeX2rEItFSM+6hCRGENJMF1QeZi7BGL +J6ryjEYuE2G4yeRCd7L4lU5iswHeqS5Q9cPQyqPbcHLRjhDgXw4TA2h0M9M5jVlgtdk QpN/2fX/NZAc0wMOkxH+em8RNeUo92SLbAHRg=
- References: <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