Re: [RFC] tools lib traceevent: How to do library versioning being in the Linux kernel source?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [RFC] tools lib traceevent: How to do library versioning being in the Linux kernel source?
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Date: Thu, 2 Jan 2020 18:58:53 -0500
- Cc: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>, Namhyung Kim <namhyung@xxxxxxxxxx>, Masami Hiramatsu <mhiramat@xxxxxxxxxx>, Linux Trace Devel <linux-trace-devel@xxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- In-reply-to: <20200102234950.GA14768@krava>
- References: <20200102122004.216c85da@gandalf.local.home> <20200102234950.GA14768@krava>
On Fri, 3 Jan 2020 00:49:50 +0100
Jiri Olsa <jolsa@xxxxxxxxxx> 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).
We can have the tools/lib/traceevent be the main source, but then just
copy it to the stand alone for releases.
Sudip, would this work for you too? (and yes, I plan on acking that
patch for the -ldl change, after looking at it a little bit more).
-- Steve
[Index of Archives]
[Linux USB Development]
[Linux USB Development]
[Linux Audio Users]
[Yosemite Hiking]
[Linux Kernel]
[Linux SCSI]