all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 'core-updates' spring 2018
Date: Mon, 26 Mar 2018 16:09:11 +0200	[thread overview]
Message-ID: <87lgefc4jc.fsf@gnu.org> (raw)
In-Reply-To: <87h8p3jfke.fsf@fastmail.com> (Marius Bakke's message of "Mon, 26 Mar 2018 12:29:05 +0200")

Hello!

Marius Bakke <mbakke@fastmail.com> skribis:

> 'core-updates' has seen a lot of changes recently.  Some of the goodies
> include HTTP/2 support in curl, binutils 2.30, glibc 2.27, reproducible
> Python bytecode, gnu-build-system will automatically run 'autoreconf' if
> necessary, warnings will be issued about snippets and phases not
> returning #t, and much more.
>
> Are there other things that should go in?
>
> Let's set a date for "freezing" it, after which it will be started on
> Hydra and only bugfixes are allowed.  How about Monday, April 2nd?

Sounds good to me!  Save the date!  :-)

For those wondering how to keep the branch active in the meantime ;-), a
useful thing to do would be to put a few key packages on a diet.  For
instance, python and llvm are pretty big and it would be good to see how
we could make them smaller.

For Python specifically, it may be that we can make “python-minimal” the
new python, and build the sqlite, readline, tcl/tk stuff as separate
packages altogether.

Ludo’.

  reply	other threads:[~2018-03-26 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 10:29 'core-updates' spring 2018 Marius Bakke
2018-03-26 14:09 ` Ludovic Courtès [this message]
2018-03-26 18:34 ` Ricardo Wurmus
2018-03-27 12:03   ` Gábor Boskovits
2018-03-28 19:46     ` Ricardo Wurmus
2018-03-27 17:43   ` Marius Bakke
2018-03-28 13:32     ` Ricardo Wurmus
2018-03-29 11:29       ` Ludovic Courtès
2018-03-30  9:26       ` glibc fallback code when ‘prlimit64’ is missing Ludovic Courtès
2018-04-01 10:37         ` Ludovic Courtès
2018-03-27 20:28 ` 'core-updates' spring 2018 Mark H Weaver

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=87lgefc4jc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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 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.