This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Systemtap Client/Server Update


Hi Dave,

Dave Brolley wrote:
> Masami Hiramatsu wrote:
>> Hi Dave,
>> Thank you for updating.
>>
>> I checked your changes on systemtap.spec and found all above tools
>> were included in systemtap package instead of systemtap-runtime.
>> stap-find-servers seems to be used by client. If so, please move it
>> to under "%files runtime" section.
>>   
> I don't understand why the client/server and related scripts should be 
> part of the runtime. They
> collectively provide a wrapper for the stap program itself, so should 
> they not be part of the same
> section as %{_bindir}/stap?

No, I recommend you to move only "client-side" scripts to
systemtap-runtime package(the same section as %{_bindir/staprun}).
So, "server-side" scripts should be left in systemtap package.

I think users want to use those client-side scripts without
installing server-side scripts and stap itself.

>> And also, could you make clear what packages are required for those
>> server/client scripts?
>> As far as I can see, it seems that avahi-tools is needed for those
>> scripts. in that case, it might be better to add those packages to
>> "Requires:" in "%package runtime" section.
>>   
> Yes, avahi-tools is needed. nc is also currently used. How do I find out 
> which package it comes in (if any)?

You can find which package provides a file by using rpm command;
$ rpm -qf /path/to/file

Thank you,


> 
> Dave
> 

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division

e-mail: mhiramat@redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]