mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/3] libtracefs: new package
Date: Fri, 10 Jan 2025 11:34:45 +0100	[thread overview]
Message-ID: <20250110103445.4m57fxrzbdtzyhtf@pengutronix.de> (raw)
In-Reply-To: <Z4DbKik6UoE956Sq@pengutronix.de>

On Fri, Jan 10, 2025 at 09:32:42AM +0100, Michael Olbrich wrote:
> On Wed, Jan 08, 2025 at 11:09:52AM +0100, Roland Hieber wrote:
> > On Tue, Dec 10, 2024 at 11:56:28AM +0100, Lucas Stach wrote:
> > > Linux kernel trace filesystem library, which has been
> > > split out from trace-cmd and kernelshark.
> > > 
> > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > > ---
> > >  rules/libtracefs.in   |  9 +++++++
> > >  rules/libtracefs.make | 59 +++++++++++++++++++++++++++++++++++++++++++
> > >  2 files changed, 68 insertions(+)
> > >  create mode 100644 rules/libtracefs.in
> > >  create mode 100644 rules/libtracefs.make
> > > 
> > > diff --git a/rules/libtracefs.in b/rules/libtracefs.in
> > > new file mode 100644
> > > index 000000000000..0f1793a5ee96
> > > --- /dev/null
> > > +++ b/rules/libtracefs.in
> > > @@ -0,0 +1,9 @@
> > > +## SECTION=system_libraries
> > > +
> > > +config LIBTRACEFS
> > > +	tristate
> > > +	select HOST_MESON
> > > +	select LIBTRACEEVENT
> > > +	prompt "libtracefs"
> > > +	help
> > > +	  Linux kernel trace filesystem library
> > > diff --git a/rules/libtracefs.make b/rules/libtracefs.make
> > > new file mode 100644
> > > index 000000000000..12f0c6e7972c
> > > --- /dev/null
> > > +++ b/rules/libtracefs.make
> > > @@ -0,0 +1,59 @@
> > > +# -*-makefile-*-
> > > +#
> > > +# Copyright (C) 2024 by Lucas Stach <l.stach@pengutronix.de>
> > > +#
> > > +# For further information about the PTXdist project and license conditions
> > > +# see the README file.
> > > +#
> > > +
> > > +#
> > > +# We provide this package
> > > +#
> > > +PACKAGES-$(PTXCONF_LIBTRACEFS) += libtracefs
> > > +
> > > +#
> > > +# Paths and names
> > > +#
> > > +LIBTRACEFS_VERSION	:= 1.8.1
> > > +LIBTRACEFS_MD5		:= d16612bef28cb49e898558fe362496cc
> > > +LIBTRACEFS		:= libtracefs-$(LIBTRACEFS_VERSION)
> > > +LIBTRACEFS_SUFFIX	:= tar.xz
> > > +LIBTRACEFS_URL		:= https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git;tag=libtracefs-$(LIBTRACEFS_VERSION)
> > > +LIBTRACEFS_SOURCE	:= $(SRCDIR)/$(LIBTRACEFS).$(LIBTRACEFS_SUFFIX)
> > > +LIBTRACEFS_DIR		:= $(BUILDDIR)/$(LIBTRACEFS)
> > > +LIBTRACEFS_LICENSE	:= LGPL-2.1 + GPL-2.0
> > 
> > Correct SPDX syntax is AND instead of +. Also you need to choose between
> > -or-later and -only versions for both licenses. And fill
> > LIBTRACEFS_LICENSE_FILES.
> 
> Right, I missed that when I applied the patch. The SPDX identifiers here
> are the old syntax, so "LGPL-2.1-only AND GPL-2.0-only" is correct. I'll
> fix it.

The GPL-2.0 is only used in build scripts, so we can disregard that. I'll send a
separate patch.

 - Roland

-- 
Roland Hieber, Pengutronix e.K.          | rhi@pengutronix.de          |
Steuerwalder Str. 21                     | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686         | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-01-10 10:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 10:56 [ptxdist] [PATCH 1/3] libtraceevent: version bump 1.8.2 -> 1.8.4 Lucas Stach
2024-12-10 10:56 ` [ptxdist] [PATCH 2/3] libtracefs: new package Lucas Stach
2025-01-08 10:09   ` Roland Hieber
2025-01-10  8:32     ` Michael Olbrich
2025-01-10 10:34       ` Roland Hieber [this message]
2025-01-10  7:44   ` [ptxdist] [APPLIED] " Michael Olbrich
2024-12-10 10:56 ` [ptxdist] [PATCH 3/3] trace-cmd: version bump 2.9.7 -> 3.3.1 Lucas Stach
2025-01-10  7:44   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-01-10  7:44 ` [ptxdist] [APPLIED] libtraceevent: version bump 1.8.2 -> 1.8.4 Michael Olbrich

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=20250110103445.4m57fxrzbdtzyhtf@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox