unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Andreas Enge <andreas@enge.fr>, Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: End of beta soon? drop i686?
Date: Thu, 13 Dec 2018 13:26:49 +0100	[thread overview]
Message-ID: <f68c7adf-2117-3787-4abc-052104853405@riseup.net> (raw)
In-Reply-To: <20181212074023.GA1383@jurong>

On 2018-12-12 08:40, Andreas Enge wrote:
> On Wed, Dec 12, 2018 at 03:16:56AM +0100, Ricardo Wurmus wrote:
>>> I'm opposed to dropping i686 support.  If we dropped support for systems
>>> that are not well supported in Guix, the only system left standing would
>>> be x86_64-linux.  I believe it is of paramount importance that Guix be
>>> portable to multiple processor architectures.  Even if we are not yet
>>> able to provide a good user experience on other systems, we can still
>>> keep the bulk of our code portable and multi-architecture aware.
>>
>> I whole-heartedly agree with Mark.  We will not drop i686 support.
> 
> And a big advantage of i686, even if noone were to use it anymore, is that
> we have a large build farm capacity, since it is built on the x86_64 machines.
> So it can act as our "canary in the mine", warning of portability problems.

Thanks for sharing your views on this.

I suggest we clearly state in the download page and or in the manual 
(Limitations) that i686 is a somewhat rough experience with not as many 
substitutes as x86_64 and might have more bugs too.

-- 
Cheers
Swedebugia

  reply	other threads:[~2018-12-13 12:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11  7:58 End of beta soon? drop i686? swedebugia
2018-12-11  9:19 ` ng0
2018-12-12  2:15   ` Ricardo Wurmus
2018-12-12  9:33     ` ng0
2018-12-11 20:02 ` Mark H Weaver
2018-12-11 20:22   ` Danny Milosavljevic
2018-12-11 23:14     ` Mark H Weaver
2018-12-12 17:52     ` Mark H Weaver
2018-12-12  2:16   ` Ricardo Wurmus
2018-12-12  7:40     ` Andreas Enge
2018-12-13 12:26       ` swedebugia [this message]
2018-12-12 16:19 ` Joshua Branson
2018-12-12 23:27   ` Mark H Weaver
2018-12-12 22:33 ` George Clemmer
  -- strict thread matches above, loose matches on Subject: below --
2018-12-12 17:52 Mark H Weaver

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=f68c7adf-2117-3787-4abc-052104853405@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).