On Thu, Jan 2, 2020 at 11:58 PM Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > 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). Debian is building libbpf from kernel tree. > > 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). If it moves to a separate repo then I guess we will need to move it out of the debian kernel and create a separate package. Might be better if we do for libbpf also. (Adding Ben). Ben? -- Regards Sudip
|