pre-compiled systemtap modules (try 2)

[David Smith]

Frank Ch. Eigler wrote:
> We should consider separating the compile / run front-ends into
> separate programs entirely, perhaps by promoting and renaming stpd
> ("staprun")?  This makes sense further because we will want to make it
> possible to install only a small subset of systemtap itself on a
> deployment machine in order to run a pre-compiled script.

OK, in the interests of furthering this, I'm attaching a patch.  This 
renames 'stpd' to 'staprun' and moves it to /usr/bin.  The testsuite has 
been modified to use 'staprun' instead of 'stpd'.  The spec file has 
been modified to output 2 packages instead of 1: "systemtap" and 
"systemtap-runtime" (currently "systemtap-runtime" just has staprun in it).

I was able to install both rpms, compile a systemtap module, remove the 
"systemtap" rpm (leaving the "systemtap-runtime" rpm behind), and run 
the module.

There is still documentation work to be done (at least).

Comments?

-- 
David Smith
dsmith@redhat.com
Red Hat, Inc.
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: staprun.patch
Type: text/x-patch
Size: 16835 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/systemtap/attachments/20060921/c093b46d/attachment.bin>