unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: core-updates frozen
Date: Sun, 15 Jun 2014 22:25:25 +0200	[thread overview]
Message-ID: <871tuphqdm.fsf@gnu.org> (raw)
In-Reply-To: <87k38ih4cr.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 15 Jun 2014 12:08:52 +0200")

ludo@gnu.org (Ludovic Courtès) skribis:

> ludo@gnu.org (Ludovic Courtès) skribis:
>
>> As discussed before, we’ll merge the branch before June 13th.
>
> The branch is now frozen.  Hydra is building it all now, and unless
> something goes wrong, I’ll merge it once it’s done building it.

I just fixed a mistake, which triggers a rebuild: commit 953c9fc changed
ncurses so that it builds a separate libtinfo library, which I thought
was a common and good thing.  Here’s what’s at stake, per ncurses’
INSTALL:

    --with-termlib[=XXX]
	When building the ncurses library, organize this as two parts:  the
	curses library (libncurses) and the low-level terminfo library
	(libtinfo).  This is done to accommodate applications that use only
	the latter.  The terminfo library is about half the size of the total.

	If an option value is given, that overrides the name of the terminfo
	library.  For instance, if the wide-character version is built, the
	terminfo library would be named libtinfow.  But the libtinfow interface
	is upward compatible from libtinfo, so it would be possible to overlay
	libtinfo.so with a "wide" version of libtinfow.so by renaming it with
	this option.

But it turns out that most packages don’t expect it this way, and in
fact recent distros don’t seem to do it; furthermore, we don’t have any
package that expects libtinfo separately at this point.  Hence the
revert in 7190ae7 (see the log for details.)

Ludo’.

  reply	other threads:[~2014-06-15 20:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14  6:51 core-updates is back Ludovic Courtès
2014-04-15  7:45 ` gmp-6.0.0a Andreas Enge
2014-04-15  9:37   ` gmp-6.0.0a Ludovic Courtès
2014-04-15  9:46     ` gmp-6.0.0a Andreas Enge
2014-04-15 15:36       ` gmp-6.0.0a Ludovic Courtès
2014-04-16  6:15         ` gmp-6.0.0a Andreas Enge
2014-06-06 13:33 ` core-updates is back Ludovic Courtès
2014-06-15 10:08 ` core-updates frozen Ludovic Courtès
2014-06-15 20:25   ` Ludovic Courtès [this message]
2014-06-16  0:47   ` Mark H Weaver
2014-06-16  7:43     ` Ludovic Courtès
2014-06-16 15:19       ` Mark H Weaver
2014-06-18 16:39       ` Mark H Weaver
2014-06-18 17:03         ` Mark H Weaver
2014-06-18 20:23         ` Ludovic Courtès
2014-06-18 20:42           ` Ludovic Courtès
2014-06-20 21:50   ` 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=871tuphqdm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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).