unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Updating tzdata freely
Date: Sun, 12 Mar 2017 19:14:55 +0100	[thread overview]
Message-ID: <874lyyjra8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170309184304.GA8957@jasmine>

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

Leo Famulari <leo@famulari.name> writes:

> After creating a special "for tests only" xorg-server package for GTK+'s
> test suite recently, I started thinking about what other packages could
> receive the same treatment.
>
> Tzdata is an important package to keep up to date. Amazingly, some
> governments do announce time zone changes only days or weeks before they
> take effect. Without an up-to-date tzdata, users' clocks will be wrong
> in those locales.
>
> Currently, updating tzdata will cause about 1400 package rebuilds.
> However, if don't use the primary tzdata package in the test suites of
> glib and R, a tzdata update will only cause ~388 rebuilds.
>
> I checked that glib and R do not retain any references to tzdata after
> they are built, so we could create a tzdata package with a "fixed"
> version that will not be updated very often.
>
> So, we could update this package more freely, at the cost of some extra
> complexity in package maintenance.
>
> What do you think?

This sounds good; I was thinking the same after seeing the tzdata update
in core-updates. "libical" still causes a fair amounts of rebuilds, but
it's a lot more manageable than the current 1315 packages :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2017-03-12 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 18:43 Updating tzdata freely Leo Famulari
2017-03-10 22:33 ` Ludovic Courtès
2017-03-12 18:14 ` Marius Bakke [this message]
2017-03-13  2:32   ` Leo Famulari

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=874lyyjra8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.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 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).