From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
users@linux.kernel.org
Subject: Re: [RFC] tools lib traceevent: How to do library versioning being in the Linux kernel source?
Date: Mon, 6 Jan 2020 13:26:23 -0300 [thread overview]
Message-ID: <20200106162623.GA11285@kernel.org> (raw)
In-Reply-To: <20200106151902.GB236146@krava>
Em Mon, Jan 06, 2020 at 04:19:02PM +0100, Jiri Olsa escreveu:
> On Fri, Jan 03, 2020 at 06:16:14PM -0500, Steven Rostedt wrote:
> >
> > [ Added Konstantin and kernel.org users mailing list ]
> >
> > On Fri, 3 Jan 2020 14:36:40 +0100
> > Jiri Olsa <jolsa@redhat.com> wrote:
> >
> > > On Thu, Jan 02, 2020 at 06:58:53PM -0500, Steven Rostedt wrote:
> > > > On Fri, 3 Jan 2020 00:49:50 +0100
> > > > Jiri Olsa <jolsa@redhat.com> wrote:
> > > >
> > > > > > Should we move libtraceevent into a stand alone git repo (on
> > > > > > kernel.org), that can have tags and branches specifically for it? We
> > > > > > can keep a copy in the Linux source tree for perf to use till it
> > > > >
> > > > > so libbpf 'moved' for this reason to github repo,
> > > > > but keeping the kernel as the true/first source,
> > > > > and updating github repo when release is ready
> > > > >
> > > > > libbpf github repo is then source for fedora (and others)
> > > > > package
> > > >
> > > > Ah, so perhaps I should follow this? I could keep it a kernel.org repo
> > > > (as I rather have it there anyway).
> > >
> > > sounds good, and if it works out, we'll follow you with libperf :-)
> > >
> > > if you want to check on the libbpf:
> > > https://github.com/libbpf/libbpf
> > >
> > > there might be some syncs scripts worth checking
> >
> > I wonder if there should be a:
> >
> > git://git.kernel.org/pub/scm/utils/lib/
> >
> > directory to have:
> >
> > git://git.kernel.org/pub/scm/utils/lib/traceevent/
> > git://git.kernel.org/pub/scm/utils/lib/libbpf/
> > git://git.kernel.org/pub/scm/utils/lib/libperf/
>
> we could loose the 'lib' and just have:
>
> git://git.kernel.org/pub/scm/utils/lib/perf/
So, we have:
https://www.kernel.org/pub/linux/kernel/tools/perf/
trying to mimic the kernel sources tree structure, so perhaps we could
have:
https://www.kernel.org/pub/linux/kernel/tools/lib/{perf,traceevent}/
To continue that directory tree mirror?
> > That could hold the libraries that are tight to the kernel?
> I don't think libbpf will change now after they are settled in github,
> but we could consider this for libperf
>
> jirka
--
- Arnaldo
next prev parent reply other threads:[~2020-01-06 16:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 17:20 [RFC] tools lib traceevent: How to do library versioning being in the Linux kernel source? Steven Rostedt
2020-01-02 18:42 ` Arnaldo Carvalho de Melo
2020-01-02 23:46 ` Steven Rostedt
2020-01-02 22:43 ` Sudip Mukherjee
2020-01-03 23:19 ` Steven Rostedt
2020-01-07 13:15 ` Namhyung Kim
2020-01-02 23:49 ` Jiri Olsa
2020-01-02 23:58 ` Steven Rostedt
2020-01-03 0:09 ` Sudip Mukherjee
2020-01-03 13:36 ` Jiri Olsa
2020-01-03 18:29 ` Sudip Mukherjee
2020-01-03 23:16 ` Steven Rostedt
2020-01-06 15:19 ` Jiri Olsa
2020-01-06 16:26 ` Arnaldo Carvalho de Melo [this message]
2020-01-06 16:36 ` Steven Rostedt
2020-01-06 19:47 ` Arnaldo Carvalho de Melo
2020-01-06 20:14 ` Konstantin Ryabitsev
2020-01-06 22:00 ` Arnaldo Carvalho de Melo
2020-01-06 20:47 ` [kernel.org users] " Jason Gunthorpe
2020-01-06 20:52 ` Steven Rostedt
2020-01-07 17:44 ` Jason Gunthorpe
2020-01-06 18:22 ` Konstantin Ryabitsev
2020-01-03 12:17 ` Masami Hiramatsu
2020-01-03 23:12 ` Steven Rostedt
2020-01-05 13:18 ` Masami Hiramatsu
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=20200106162623.GA11285@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=users@linux.kernel.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.