All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Chikunov <vt@altlinux.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org, "Dmitry V. Levin" <ldv@altlinux.org>
Subject: Where is proper libtraceevent plugins tree?
Date: Mon, 3 Aug 2020 00:09:04 +0300	[thread overview]
Message-ID: <20200802210904.iotublzj5bmp32sl@altlinux.org> (raw)

Steven,

I am trying to rework trace-cmd and perf packages for ALT Linux. But, I
found that trace-cmd 2.9 builds and installs /usr/lib64/traceevent/plugins
and perf builds and installs /usr/lib64/traceevent/plugins (some plugins
have same names, some different).

This would create bad files conflict in packaging system.

Both source trees seems to be recently updated:
  linux/tools/lib/traceevent/plugins/ and
  trace-cmd/lib/traceevent/plugins/

(trace-cmd 2.8 it installed these same plugins in /usr/lib64/trace-cmd/plugins).

How it's supposed to build and install (perf and trace-cmd) without conflicts?
Where is true (lib?)traceevent source tree?

Thanks,


             reply	other threads:[~2020-08-02 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-02 21:09 Vitaly Chikunov [this message]
2020-08-03  0:25 ` Where is proper libtraceevent plugins tree? Steven Rostedt

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=20200802210904.iotublzj5bmp32sl@altlinux.org \
    --to=vt@altlinux.org \
    --cc=ldv@altlinux.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.