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] |
OK. I understand now and agree.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.
OK. Turns out that there is a 'nc' package. I'm adding 'Requires: avahi-tools nc' to both the runtime section and to the systemtap section.You can find which package provides a file by using rpm command;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.
$ rpm -qf /path/to/file
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |