From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix beyond 1.0: let’s have a roadmap!
Date: Thu, 27 Jun 2019 23:17:16 +0200 [thread overview]
Message-ID: <877e96u3s3.fsf@gnu.org> (raw)
In-Reply-To: <87d0izq7oq.fsf@yucca> (Vagrant Cascadian's message of "Thu, 27 Jun 2019 10:06:29 -0700")
Hello,
Vagrant Cascadian <vagrant@debian.org> skribis:
> On 2019-06-27, Ludovic Courtès wrote:
>> People rightfully suggested having some sort of a roadmap for what’s
>> next.
> ...
>> What do *you* want Guix to address in the future?
>
> A few architecture support issues come to mind:
>
> * Architectures
>
> ** TODO system/installer images for armhf
> ** TODO system/installer images for aarch64
> ** TODO riscv64 support
> ** TODO ppc64el(le?)/power9 support
>
> (maybe move GNU/Hurd to this category too?)
Sounds good to me!
>> * core
> ...
>> ** TODO [[https://gitlab.com/rutger.van.beusekom/gash][Gash]] used instead of Bash during bootstrap
>
> What about a full bootstrap using MES and company?
It’s already in ‘core-updates’ so I consider it “done”, at least for
this initial variant. But yeah, I expect there’ll be incremental
improvements that will allow us to gradually reduce the set of bootstrap
binaries, and also more architecture support (I know people have worked
on ARM support recently.)
>> * miscellaneous
> ...
>> ** TODO Debian package for Guix is available
>
> Working on it! kind of stalled out at the moment waiting on processes
> within Debian... once the current release is done (scheduled for early
> July), things will hopefully start moving again.
Yay! \o/
Ludo’.
next prev parent reply other threads:[~2019-06-27 21:17 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 16:05 Guix beyond 1.0: let’s have a roadmap! Ludovic Courtès
2019-06-27 16:36 ` P
2019-06-27 21:12 ` Ludovic Courtès
2019-06-27 17:06 ` Vagrant Cascadian
2019-06-27 21:17 ` Ludovic Courtès [this message]
2019-06-27 18:53 ` Jakob L. Kreuze
2019-06-27 21:18 ` Ludovic Courtès
2019-06-27 19:02 ` Alex Griffin
2019-06-27 22:33 ` swedebugia
2019-06-28 6:11 ` Julien Lepiller
2019-06-28 16:13 ` John Soo
2019-07-01 9:14 ` Ludovic Courtès
2019-07-01 11:57 ` Pierre Neidhardt
2019-07-07 14:15 ` Ludovic Courtès
2019-06-30 13:48 ` Giovanni Biscuolo
2019-07-01 9:16 ` Ludovic Courtès
2019-07-05 7:55 ` Giovanni Biscuolo
2019-07-01 10:05 ` Ludovic Courtès
2019-07-01 13:12 ` Alex Griffin
2019-07-05 8:35 ` Guix UCI comparison (was Re: Guix beyond 1.0: let’s have a roadmap!) Giovanni Biscuolo
2019-07-07 14:09 ` Guix beyond 1.0: let’s have a roadmap! Ludovic Courtès
2019-06-27 19:33 ` Svante Signell
2019-06-27 21:25 ` Ludovic Courtès
2019-06-27 20:28 ` Thompson, David
2019-07-01 9:36 ` Ludovic Courtès
2019-07-01 10:39 ` Hartmut Goebel
2019-07-01 9:37 ` Ludovic Courtès
2019-06-27 22:01 ` Pierre Neidhardt
2019-06-27 22:24 ` Julien Lepiller
2019-07-01 9:48 ` Ludovic Courtès
2019-06-28 16:54 ` znavko
2019-06-28 17:07 ` swedebugia
2019-06-28 17:17 ` znavko
2019-06-29 1:35 ` ison
2019-06-29 4:51 ` pelzflorian (Florian Pelz)
2019-07-01 9:51 ` Ludovic Courtès
2019-06-30 13:13 ` Giovanni Biscuolo
2019-06-30 13:38 ` Robert Vollmert
2019-07-01 9:55 ` Ludovic Courtès
2019-07-05 11:47 ` Robert Vollmert
2019-07-09 10:22 ` Ricardo Wurmus
2019-07-09 10:58 ` Robert Vollmert
[not found] ` <877e97vws8.fsf%40gnu.org504D1A97-2EBD-46A1-85B8-091C923DD6A1@vllmrt.net>
2019-07-26 7:00 ` Ben Sturmfels
2019-07-26 8:27 ` Pierre Neidhardt
2019-08-22 20:59 ` Ludovic Courtès
2019-06-30 13:28 ` Christopher Lemmer Webber
2019-07-01 9:57 ` Ludovic Courtès
2019-07-01 11:47 ` Pierre Neidhardt
2019-06-30 13:59 ` Giovanni Biscuolo
2019-07-01 9:58 ` Ludovic Courtès
2019-07-09 13:32 ` P
2019-07-11 10:11 ` Ricardo Wurmus
2019-07-11 15:17 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2019-06-28 18:57 Jesse Gibbons
2019-07-01 10:14 ` zimoun
2019-07-01 19:38 ` Jesse Gibbons
2019-07-06 12:50 matias_jose_seco
2019-07-07 14:20 ` 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=877e96u3s3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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).