all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Ideas for Summer of Code 2017
Date: Tue, 14 Feb 2017 17:25:16 +0100	[thread overview]
Message-ID: <87k28sspsj.fsf@gnu.org> (raw)
In-Reply-To: <20170214093051.lril7mtynlnpm2oz@wasp> (ng0's message of "Tue, 14 Feb 2017 09:30:51 +0000")

ng0 <contact.ng0@cryptolab.net> skribis:

> On 17-02-14 10:10:55, Ludovic Courtès wrote:
>> Christopher Allan Webber <cwebber@dustycloud.org> skribis:
>> 
>> > One interesting change from when this was defined last year and this
>> > year is that the "extensible event loop" one has some candidates to pick
>> > from, via guile a-sync, fibers, and 8sync.
>> >
>> > However using any of those would require Shepherd being pinned to Guile
>> > 2.2.  Maybe not a problem; it could be a branch, and Guile 2.2 stable
>> > looks not so far away.
>> 
>> Yes, I think it’d be reasonable to have Shepherd rely on 2.2.
>> 
>> In fact, we should start moving all of our infrastructure to 2.2.  There
>> are still a couple of issues to be addressed I think, but now’s the time
>> to explore.
>> 
>> Ludo’.
>> 
>
> Could that be a project as well, to move the guile parts to 2.2 or is
> this too lowkey and too little for GSoC?

Ideally, there won’t be much to do to switch to 2.2.  :-)

Guix itself builds with 2.2, albeit slowly at the moment.  We’d need to
routinely use 2.1 to see if there other issues.

Of all the dependencies of Guix, I think only Guile-SSH needs “porting”
to 2.2, but even that should not be too much work.

So it’s mostly about ironing things out and making sure we can
transition smoothly enough, rather than a development project of its
own.

Ludo’.

      reply	other threads:[~2017-02-14 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 21:43 Ideas for Summer of Code 2017 Mathieu Lirzin
2017-01-21 15:09 ` Ludovic Courtès
2017-02-13 19:57 ` Christopher Allan Webber
2017-02-13 20:40   ` David Craven
2017-02-13 20:51     ` Adonay Felipe Nogueira
2017-02-13 20:58       ` David Craven
     [not found]         ` <87lgt97ob6.fsf@openmailbox.org>
2017-02-13 22:31           ` David Craven
2017-02-14  9:07     ` Ludovic Courtès
2017-02-14  9:10   ` Ludovic Courtès
2017-02-14  9:30     ` ng0
2017-02-14 16:25       ` Ludovic Courtès [this message]

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=87k28sspsj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cwebber@dustycloud.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 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.