unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: fis trivial <ybbs.daans@hotmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Roadmap for Guix 1.0
Date: Tue, 4 Sep 2018 22:55:57 +0000	[thread overview]
Message-ID: <BLUPR16MB0500C295276F2A54892A5EEE92030@BLUPR16MB0500.namprd16.prod.outlook.com> (raw)
In-Reply-To: <878t5udq9u.fsf@gnu.org>


Ludovic Courtès writes:

> Hello Guix!
>
> I’ve pushed to guix/maintenance.git a list of things that IMO we should
> do or might want to do for 1.0, with the understanding that 1.0 should
> happen in 2018 (or early 2019 at the latest!).  :-)
>
>   https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/1.0.org
>
> The list focuses on “big item” features and tasks, omitting routine bug
> fixes and improvements.  Some of these items don’t require a lot of work
> or expertise though, so hopefully there’s enough on everyone’s plate.
>
> Feel free to comment, volunteer, add items (but not too many!), remove
> items, promote items, etc.  Committers should feel free to edit the file
> directly in maintenance.git, especially to mark things as done.  ;-)
>
> Copy of the file attached below.
>
> Ludo’.
>
> PS: I’m starting the discussion but will go AFK soon after sending this
>     message.  :-)

Hi Ludovic,

For near future version of GUIX, maybe 1.1, would it be possible to:

    Upgrade to latest GCC as base compiler

    Use gold linker as default

Based on experience, newer GCC and gold linker could reduce compilation time
and memory requirement dramatically.  It would be beneficial to both build
farm which have heavy load and laptop users who have very limited memory.

Thanks.
-- 
Jiaming

  parent reply	other threads:[~2018-09-04 22:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29 15:18 Roadmap for Guix 1.0 Ludovic Courtès
2018-07-30  1:23 ` Pjotr Prins
2018-07-30  9:02   ` Nils Gillmann
2018-07-30 12:47     ` Pierre Neidhardt
2018-08-19 11:06       ` LVM support Ludovic Courtès
2018-08-29 16:12   ` Roadmap for Guix 1.0 Amirouche Boubekki
2018-08-30 11:46     ` Pierre Neidhardt
2018-08-30 12:04       ` Ludovic Courtès
2018-08-30 12:57         ` Ricardo Wurmus
2018-08-30 14:20           ` Tobias Geerinckx-Rice
2018-08-30 15:17             ` Nils Gillmann
2018-08-30 19:13           ` George Clemmer
2018-08-30 20:12             ` Gábor Boskovits
2018-08-31 14:25               ` George Clemmer
2018-08-31 15:45                 ` Vincent Legoll
2018-08-31 15:54                   ` Amirouche Boubekki
2018-09-01  7:36                     ` rchar01
2018-09-01  9:27                       ` Pjotr Prins
2018-09-01 10:09                         ` Nils Gillmann
2018-08-30 15:36         ` George Clemmer
2018-08-30 17:11         ` Hartmut Goebel
2018-08-30 18:17         ` Jan Nieuwenhuizen
2018-08-30 21:45       ` Taylan Kammer
2018-07-30  5:08 ` Chris Marusich
2018-07-30  7:33   ` Pierre Neidhardt
2018-08-19 11:19     ` Ludovic Courtès
2018-08-19 11:11   ` Ludovic Courtès
2018-08-20  1:12     ` Chris Marusich
2018-08-30 19:34       ` Ricardo Wurmus
2018-08-19 21:52 ` Amirouche Boubekki
2018-08-20  7:44   ` Ricardo Wurmus
2018-08-29 16:05     ` Amirouche Boubekki
2018-09-04 22:55 ` fis trivial [this message]
2018-09-04 23:09   ` Adam Van Ymeren

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=BLUPR16MB0500C295276F2A54892A5EEE92030@BLUPR16MB0500.namprd16.prod.outlook.com \
    --to=ybbs.daans@hotmail.com \
    --cc=guix-devel@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).