[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADVatmP1iZdiWWqs-ZujAeXiCvYYJpNvoPt3K+GFfL5a6vyJGA@mail.gmail.com>
Date: Mon, 12 Oct 2020 16:32:00 +0100
From: Sudip Mukherjee <sudipm.mukherjee@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Jiri Olsa <jolsa@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
Linux Trace Devel <linux-trace-devel@...r.kernel.org>,
Zamir SUN <sztsian@...il.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
zsun@...hat.com, Vitaly Chikunov <vt@...linux.org>,
Tzvetomir Stoyanov <tstoyanov@...are.com>,
Yordan Karadzhov <ykaradzhov@...are.com>,
Ben Hutchings <ben@...adent.org.uk>,
Tony Jones <tonyj@...e.de>, John Kacur <jkacur@...hat.com>,
Clark Williams <williams@...hat.com>, powertop@...ts.01.org,
Al Stone <ahs3@...ian.org>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Subject: Re: [ANNOUNCE] libtraceevent.git
On Mon, Oct 12, 2020 at 4:19 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Mon, 12 Oct 2020 12:12:08 +0200
> Jiri Olsa <jolsa@...hat.com> wrote:
>
> > On Wed, Oct 07, 2020 at 01:07:50PM -0400, Steven Rostedt wrote:
> > > I split out tools/lib/traceevent from the kernel tree using "git subtree",
> > > which recreates all the commits of a directory and makes that directory a
> > > stand alone. I then updated the Makefiles, and copied over some of the
> > > header files used to build the library. I pushed this up to:
> > >
> > > https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
> > >
> > > My hope is that this will now be the source of all updates to the
> > > libtraceevent library that can be used as a stand alone package that both
> > > perf and tracecmd can use. I would also like powertop and rasdaemon to use
> > > this as well.
> >
> > hi,
> > I'm adding this as fedora package, is there a source arhive somewhere
> > in git.kernel.org for libtraceevent that spec could download?
> >
>
> Hi Jiri!
>
> Once it's shown that it works for all the package maintainers, I will tag
> it which should create the tarballs automatically on the above link. But I
> wanted to fix all the packaging bugs before doing so. I hope this doesn't
> make it into a catch-22. Where you can't package till there's a source
> tarball, but I can't make a source tarball until I know you can package
> it ;-)
For Debian I have raised https://bugs.debian.org/971976 but I will
package it locally today just to check there is no packaging bugs for
our packaging.
--
Regards
Sudip
Powered by blists - more mailing lists