Linux-Trace-Devel Archive mirror
 help / color / mirror / Atom feed
From: Aleksander Trofimowicz <trof@n90.eu>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH] libtracefs meson: Use SemVer in the build description
Date: Thu, 14 Mar 2024 16:20:43 +0000	[thread overview]
Message-ID: <87v85okco4.fsf@mx.n90.eu> (raw)

Meson adheres to RPM rules while exercising version
sorting. Therefore 1.8 < 1.8.0; Meson-driven builds of trace-cmd
are broken since b86599e459 since a dependency requirement
cannot be met.

Signed-off-by: Aleksander Trofimowicz <trof@n90.eu>
---
 meson.build | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meson.build b/meson.build
index 3156f1c..91ee79a 100644
--- a/meson.build
+++ b/meson.build
@@ -6,7 +6,7 @@ project(
     'libtracefs', ['c'],
     meson_version: '>= 0.50.0',
     license: 'LGPL-2.1',
-    version: '1.8',
+    version: '1.8.0',
     default_options: [
         'c_std=gnu99',
         'buildtype=debug',
--
2.44.0
--
at

             reply	other threads:[~2024-03-14 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 16:20 Aleksander Trofimowicz [this message]
2024-03-14 16:43 ` [PATCH] libtracefs meson: Use SemVer in the build description Steven Rostedt

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=87v85okco4.fsf@mx.n90.eu \
    --to=trof@n90.eu \
    --cc=linux-trace-devel@vger.kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).