From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: 66733@debbugs.gnu.org
Subject: [bug#66733] [PATCH v2] gnu: abseil-cpp: Update to 20230802.1.
Date: Wed, 22 Nov 2023 15:41:40 +0100 [thread overview]
Message-ID: <87o7fllujf.fsf@gnu.org> (raw)
In-Reply-To: <20231024193756.253478-1-code@greghogan.com> (Greg Hogan's message of "Tue, 24 Oct 2023 19:37:49 +0000")
Hi,
Greg Hogan <code@greghogan.com> skribis:
> v2: fix for wording in commit header.
>
> * gnu/packages/cpp.scm (abseil-cpp): Update to 20230802.1.
> [arguments]<#:phases>: Add phase to set timezone environment variable.
> * gnu/packages/cpp.scm (abseil-cpp-20220623.1): Keep old version.
> * gnu/packages/cpp.scm (abseil-cpp-for-c++-standard): Accept package to
> inherit from.
> * gnu/packages/cpp.scm (abseil-cpp-cxxstd11, abseil-cpp-cxxstd17):
> Inherit from latest supported version.
[...]
> + #~(modify-phases #$phases
> + (add-before 'check 'set-env-vars
> + (lambda* (#:key inputs #:allow-other-keys)
> + ;; absl_time_test requires this environment variable.
> + (setenv "TZDIR" (string-append (assoc-ref %build-inputs "source")
This could be written like so:
(setenv "TZDIR" (string-append #$(package-source this-package) …))
or referring to ‘inputs’ rather than ‘%build-inputs’.
Apart from that, it LGTM… but time has passed and it no longer
applies. :-/
Could you rebase it and resend?
Thanks and apologies for the delay!
Ludo’.
next prev parent reply other threads:[~2023-11-22 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 19:23 [bug#66733] [PATCH] gnu: abseil-cpp: Add to 20230802.1 Greg Hogan
2023-10-24 19:37 ` [bug#66733] [PATCH v2] gnu: abseil-cpp: Update " Greg Hogan
2023-11-22 14:41 ` Ludovic Courtès [this message]
2023-11-27 19:19 ` [bug#66733] [PATCH v3] " Greg Hogan
2023-12-04 20:55 ` bug#66733: " Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7fllujf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=66733@debbugs.gnu.org \
--cc=code@greghogan.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).