unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: 30469@debbugs.gnu.org
Subject: [bug#30469] [PATCH 0/1] Require Guile >= 2.0.14
Date: Sun, 25 Feb 2018 12:53:29 +0100	[thread overview]
Message-ID: <f40c758b-e385-5ff8-bc6d-bb91ddd9c1a1@web.de> (raw)
In-Reply-To: <87k1v280yz.fsf@gnu.org>

On 02/24/2018 11:41 PM, Ludovic Courtès wrote:>> How much of this patch
would change if it were to instead support
>> 2.0.13?  Is cutting off users of Debian stable a good idea?
> 
> I’ll double-check but I think the patch remains valid if we require
> 2.0.13.

Opensuse Leap 15 will have 2.0.14, so I would be okay with it.

> If it works I’ll commit that next week.
> 
>>> I’d also like it to be the last release that support Guile 2.0.
>>
>> Same question.
> 
> 2.2 is becoming quite widespread in distros.
> 
> Overall it’s a cost/benefit tradeoff, and we have to take into account
> that most users get Guix using the binary tarball or GuixSD.

2.2 is not as easy as I thought it would be, to bring it to openSUSE
Leap. There are packages who still require guile 2.0 (see comments in
https://build.opensuse.org/request/show/568553). And the fact that only
a handful of packages need guile, makes it not really worthwhile for
distros to have two versions of guile present like we see it for python.

It would be nice to have guix in Debian, Ubuntu, SUSE land and Red Hat
land. I think that would enable far more people to use guix.

At the moment it's not easy to install guix from source without having
guix in place, at least on openSUSE. You need those guile modules
(guile-git, guile-bytestructures) who comes with almost no build
documentation. And then you have to fiddle together guile with the right
versions...

We struggle a lot with bootstrapping rust, go, java etc, so we should
make sure that "bootstrapping" guix (install from source) is easy or at
least doable.

Best Regards
Jonathan

  reply	other threads:[~2018-02-25 11:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 15:26 [bug#30469] [PATCH 0/1] Require Guile >= 2.0.14 Ludovic Courtès
2018-02-15 15:29 ` [bug#30469] [PATCH 1/1] build: " Ludovic Courtès
2018-02-24 14:30 ` [bug#30469] [PATCH 0/1] " Eric Bavier
2018-02-24 22:41   ` Ludovic Courtès
2018-02-25 11:53     ` Jonathan Brielmaier [this message]
2018-02-27 17:23       ` Ludovic Courtès
2018-02-26  0:59     ` Eric Bavier
2018-02-26 18:49       ` bug#30469: " 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=f40c758b-e385-5ff8-bc6d-bb91ddd9c1a1@web.de \
    --to=jonathan.brielmaier@web.de \
    --cc=30469@debbugs.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).