From: ng0@n0.is
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: glibc 2.29 needs Python
Date: Sat, 1 Jun 2019 12:04:10 +0000 [thread overview]
Message-ID: <20190601120410.xkuclz2t2w2fqkzm@uptimegirl> (raw)
In-Reply-To: <878sulsncp.fsf@gnu.org>
Jan Nieuwenhuizen transcribed 759 bytes:
> Ludovic Courtès writes:
>
> Hi!
>
> >>> I started looking at what it would take to upgrade glibc to 2.29 on
> >>> ‘core-updates’. Bad news: it depends on Python.
> >>
> >> I had to check the date. This is for real?
> >
> > It’s not a June 1st prank, I swear!
>
> Oh, great... not.
>
> >> I’ll take a look at python-on-guile and see if we can run the scripts
> >> with it.
> >
> > That’d be sweet!
>
> Yes! ... Although...how are we -- in the far future -- going to replace
> Guile with Mes for the Guix bootstrap? Could it be that the glibc
> developers haven't seen my talk? :-/
Maintain a variant of glibc or your own libc?
It's not that far off for an Operating System, and nothing which is impossible.
> janneke
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
>
next prev parent reply other threads:[~2019-06-01 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 10:39 glibc 2.29 needs Python Ludovic Courtès
2019-05-30 11:29 ` Ricardo Wurmus
2019-05-30 12:46 ` Giovanni Biscuolo
2019-05-31 22:13 ` Ludovic Courtès
2019-06-01 8:48 ` Jan Nieuwenhuizen
2019-06-01 12:04 ` ng0 [this message]
2019-06-01 16:48 ` Ricardo Wurmus
2019-06-20 14:09 ` Ricardo Wurmus
2019-06-20 15:06 ` Danny Milosavljevic
2019-06-20 15:25 ` Ricardo Wurmus
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=20190601120410.xkuclz2t2w2fqkzm@uptimegirl \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=janneke@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.