From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Starting 'core-updates'?
Date: Fri, 31 Jan 2020 14:48:41 -0500 [thread overview]
Message-ID: <875zgrs8yu.fsf@gmail.com> (raw)
In-Reply-To: <87mua8sma4.fsf@devup.no> (Marius Bakke's message of "Mon, 27 Jan 2020 20:59:47 +0100")
Hello Marius!
Marius Bakke <mbakke@fastmail.com> writes:
> Hello Guix,
>
> The 'core-updates' branch is starting to look pretty good, and I am
> happy to report that it "works for me". :-)
>
> Some of the big changes include:
>
> * Large parts of Guix can now be cross-compiled, allowing building Guix
> System for foreign architectures without emulation.
>
> * Python was updated to 3.8.1, and most of the popular packages such as
> Pytest are at the latest available versions.
>
> * The 'libjpeg' library has been deprecated in favor of 'libjpeg-turbo'.
>
> * 'util-linux' gained a "lib" output, decreasing the closure size of
> packages that only need the libraries by ~11.5 MiB.
>
> * 'boost' now uses Python 3 by default.
>
> * 'sqlite-with-column-metadata' has been merged with 'sqlite'.
>
> * The quest to remove static libraries from core packages is ongoing.
> Many packages are a tiny bit smaller for that reason. On the flip
> side, the closure size of some packages increased, because they are
> forced to use the shared library instead of embedding a static copy.
>
> * cmake-build-system's support for cross-compilation is significantly
> improved. CMake itself also no longer bundles any of its dependencies
> (even if they were mostly unused).
>
> * Of course we have the latest versions of core packages such as glibc,
> make, sed, binutils, etc.
>
> I suggest that we set a "freeze" date shortly after FOSDEM to start
> integrating it. Are there other branches that should be included?
> Maybe wip-bootstrap or GNOME 3.34?
Congratulations! I'm using core-updates as well, it seems to be working
pretty well so far as well (except some issue with CPATH causing
compilation warnings from system libraries to be emitted when only the
project's headers should be considered (https://bugs.gnu.org/30756).
I'll be looking at ways to resolve this (going back to
CPLUS_INCLUDE_PATH and C_INCLUDE_PATH without triggering include_next
errors from glibc's headers).
Maxim
next prev parent reply other threads:[~2020-01-31 19:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 19:59 Starting 'core-updates'? Marius Bakke
2020-01-27 20:44 ` Pierre Neidhardt
2020-01-27 21:46 ` zimoun
2020-01-28 8:55 ` Mathieu Othacehe
2020-01-28 9:08 ` Christopher Baines
2020-01-28 10:47 ` Ludovic Courtès
2020-01-28 10:51 ` Ludovic Courtès
2020-01-31 19:48 ` Maxim Cournoyer [this message]
2020-02-13 15:18 ` Jan Nieuwenhuizen
2020-02-14 15:18 ` Marius Bakke
2020-02-18 6:25 ` [bug#38390] [core-updates] Scheme-only bootstrap: merge wip-bootstrap / Starting `core-updates' Jan Nieuwenhuizen
-- strict thread matches above, loose matches on Subject: below --
2018-04-21 7:54 Successfully running GNOME on core-updates + staging Mark H Weaver
2018-04-22 19:55 ` Ludovic Courtès
2018-04-23 18:13 ` Marius Bakke
2018-04-25 12:14 ` Ludovic Courtès
2018-05-01 14:12 ` Starting 'core-updates' Marius Bakke
2018-05-01 14:23 ` Leo Famulari
2018-05-01 18:23 ` Mark H Weaver
2018-05-01 20:46 ` Ludovic Courtès
2018-05-01 21:21 ` 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
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=875zgrs8yu.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--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 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).