[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200106113615.4545e3c5@gandalf.local.home>
Date: Mon, 6 Jan 2020 11:36:15 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
Cc: Jiri Olsa <jolsa@...hat.com>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Linux Trace Devel <linux-trace-devel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
users@...ux.kernel.org
Subject: Re: [RFC] tools lib traceevent: How to do library versioning being
in the Linux kernel source?
On Mon, 6 Jan 2020 13:26:23 -0300
Arnaldo Carvalho de Melo <arnaldo.melo@...il.com> wrote:
> 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?
Wouldn't that become a bit of manual work. Unlike perf, the versions
will not correspond to the Linux kernel versions. They would need to
follow library versioning.
It would at a minimum require new scripting to get this right.
-- Steve
Powered by blists - more mailing lists