From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31484@debbugs.gnu.org
Subject: [bug#31484] [PATCH] gnu: icu4c: Patch zoneinfo directory.
Date: Mon, 21 May 2018 13:15:14 -0400 [thread overview]
Message-ID: <20180521171514.GA13182@jasmine.lan> (raw)
In-Reply-To: <878t8fpfah.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
On Sat, May 19, 2018 at 10:21:42PM +0200, Ludovic Courtès wrote:
> Hello,
>
> Christopher Baines <mail@cbaines.net> skribis:
>
> > Replace the hardcoded /usr/share/zoneinfo file with a reference to the tzdata
> > package.
> >
> > * gnu/packages/icu4c.scm (icu4c)[inputs]: Add tzdata.
> > [arguments]: Add a patch-zoneinfo-directory phase.
Thanks for noticing this, Chris.
> I wonder if icu4c should instead depend on ‘tzdata-for-tests’, which is
> changed less frequently to avoid full rebuilds? Maybe Leo can comment.
tzdata-for-tests is meant to be used by packages that don't need current
time zone info. Thus, "for test suites only". We added tzdata-for-tests
to make it cheaper to update tzdata.
If icu4c needs current time zone info, it should not use
tzdata-for-tests. Chris, can you give more context about how icu4c uses
time zone information?
> I hope icu4c also honors the TZDIR environment variable, which would
> allow users to have it refer to the latest version. Do you know if
> that’s the case?
Yeah, it would be great if icu4c could just use TZDIR, which would allow
us to continue updating the time zones relatively frequently... if icu4c
actually needs the time zone database.
Already, we have problems keeping them up to date because too many
packages depend on them, and that's a problem for Guix users (clocks
will be wrong in some time zones). If we let icu4c depend on tzdata,
then we will only be able to update the time zones during core-updates,
which is not frequent enough. Currently, we can at least update tzdata
on 'staging' braches.
It indicates two general problems, IMO:
1) the lack of build farm capacity
2) it should be possible to update the time zone database without
rebuilding packages (the packages should use TZDIR)
I wonder what is done in Nixpkgs...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-21 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 12:58 [bug#31484] [PATCH] gnu: icu4c: Patch zoneinfo directory Christopher Baines
2018-05-19 20:21 ` Ludovic Courtès
2018-05-21 17:15 ` Leo Famulari [this message]
2018-05-22 12:06 ` Ludovic Courtès
2018-05-24 16:30 ` Leo Famulari
2018-06-11 18:18 ` Christopher Baines
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=20180521171514.GA13182@jasmine.lan \
--to=leo@famulari.name \
--cc=31484@debbugs.gnu.org \
--cc=ludo@gnu.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.
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).