From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26536] New: make it possible to have third-party add-on tapsets without conflicting with stap standard tapset
Date: Tue, 25 Aug 2020 15:59:48 +0000 [thread overview]
Message-ID: <bug-26536-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26536
Bug ID: 26536
Summary: make it possible to have third-party add-on tapsets
without conflicting with stap standard tapset
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
systemtap installs its own tapset/ under $prefix/..., aka. $SYSTEMTAP_TAPSET.
Third party packages like ruby and python and .... also install extension
tapsets under the same path. This is a problem if one has a private copy of
systemtap installed under a different $prefix, because then these third-party
tapsets are inaccessible. Setting
$SYSTEMTAP_TAPSET=/usr/share/systemtap/tapset probably doesn't work for these,
because the distro version would not match the stap-version runtime/ or
translator.
So we need to somehow separate the two: third-party tapsets and
stap-accompanying tapsets.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-08-25 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 15:59 fche at redhat dot com [this message]
2020-08-25 16:01 ` [Bug tapsets/26536] " mcermak at redhat dot com
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=bug-26536-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).