From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: iyzsong@envs.net, 65654@debbugs.gnu.org
Cc: "Raghav Gururajan" <rg@raghavgururajan.name>,
宋文武 <iyzsong@member.fsf.org>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#65654] [PATCH] gnu: dbus-cxx: Update to 2.4.0.
Date: Thu, 31 Aug 2023 18:58:14 +0200 [thread overview]
Message-ID: <f449c32625d8068456f6e75d14128fb5d892f1d9.camel@gmail.com> (raw)
In-Reply-To: <5686dc3309451165e7875231057a98030399a085.1693479069.git.iyzsong@member.fsf.org>
Am Donnerstag, dem 31.08.2023 um 18:51 +0800 schrieb iyzsong@envs.net:
> From: 宋文武 <iyzsong@member.fsf.org>
>
> * gnu/packages/glib.scm (dbus-cxx): Update to 2.4.0.
> [source]: Switch to git-fetch.
> [arguments]: Use g-exps. Adjust configure-flags.
> Skip 'test-machine-uuid-method' test.
> [inputs]: Remove python and glibmm. Move libsigc++ to...
> [propagated-inputs]: ...here. Add glib.
> [native-inputs]: Remove m4.
> [license]: Change to lgpl3+ and bsd-3.
> ---
> gnu/packages/glib.scm | 36 ++++++++++++++++++++----------------
> 1 file changed, 20 insertions(+), 16 deletions(-)
>
> diff --git a/gnu/packages/glib.scm b/gnu/packages/glib.scm
> index f523706449..043d506a9e 100644
> --- a/gnu/packages/glib.scm
> +++ b/gnu/packages/glib.scm
> @@ -1255,26 +1255,30 @@ (define-public dbus-c++
> (define-public dbus-cxx
> (package
> (name "dbus-cxx")
> - (version "0.12.0")
> + (version "2.4.0")
Version appears to be correct. As for whether the package works or
not, I'll defer to CI.
> (source (origin
> - (method url-fetch)
> - (uri (string-append "mirror://sourceforge/dbus-
> cxx/dbus-cxx/"
> - version "/dbus-cxx-" version
> ".tar.gz"))
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/dbus-cxx/dbus-cxx")
> + (commit version)))
> + (file-name (git-file-name name version))
> (sha256
> (base32
> -
> "1acsgpkd9v7b9jdc79ijmh9dbdfrzgkwkaff518i3zpk7y6g5mzw"))))
> +
> "0c9q2bjs4m66zq0qysyip8fnkvvjpj46rkjcvw15nhmfhzbq16ag"))))
> (build-system cmake-build-system)
> (arguments
> - `(#:configure-flags '("-DENABLE_TESTS=ON"
> - "-DENABLE_TOOLS=ON"
> - "-DENABLE_GLIBMM=ON")))
> - (inputs (list dbus
> - libsigc++
> - glibmm
> - python
> - popt
> - expat))
> - (native-inputs (list pkg-config m4))
> + (list #:configure-flags #~(list "-DBUILD_TESTING=ON"
> + "-DENABLE_TOOLS=ON"
> + "-DENABLE_GLIB_SUPPORT=ON")
> + #:phases
> + #~(modify-phases %standard-phases
> + (replace 'check
> + (lambda _
> + ;; XXX: Missing /etc/machine-id in the build
> environment.
> + (invoke "ctest" "-E" "test-machine-uuid-
> method"))))))
> + (propagated-inputs (list glib libsigc++))
> + (inputs (list dbus expat popt))
> + (native-inputs (list pkg-config))
> (synopsis "C++ wrapper for dbus")
> (description "Dbus-cxx is a C++ wrapper for dbus.\n
> It exposes the C API to allow direct manipulation and
> @@ -1288,7 +1292,7 @@ (define-public dbus-cxx
> Some codes examples can be find at:
> @url{https://dbus-cxx.github.io/examples.html}")
> (home-page "https://dbus-cxx.github.io/")
> - (license license:gpl3)))
> + (license (list license:lgpl3+ license:bsd-3))))
I think we should also mention tools/libcppgenerate or otherwise
unbundle it; judging by the name, it appears to be a native input, but
I might be wrong about that.
Cheers
next prev parent reply other threads:[~2023-08-31 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 10:51 [bug#65654] [PATCH] gnu: dbus-cxx: Update to 2.4.0 iyzsong--- via Guix-patches via
2023-08-31 16:58 ` Liliana Marie Prikler [this message]
2023-09-01 3:48 ` Maxim Cournoyer
2023-09-01 12:44 ` [bug#65654] [PATCH v2 1/2] gnu: Add libcppgenerate iyzsong--- via Guix-patches via
2023-09-01 12:44 ` [bug#65654] [PATCH v2 2/2] gnu: dbus-cxx: Update to 2.4.0 iyzsong--- via Guix-patches via
2023-09-01 14:45 ` bug#65654: " Maxim Cournoyer
2023-09-01 14:52 ` [bug#65654] [PATCH] " Maxim Cournoyer
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=f449c32625d8068456f6e75d14128fb5d892f1d9.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=65654@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=iyzsong@member.fsf.org \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.