unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: MIPS support
Date: Sun, 24 May 2020 23:03:13 +0200	[thread overview]
Message-ID: <87pnatyrji.fsf@gnu.org> (raw)
In-Reply-To: <20200518070122.GE18220@E5400> (Efraim Flashner's message of "Mon, 18 May 2020 10:01:22 +0300")

Hey!

Efraim Flashner <efraim@flashner.co.il> skribis:

> On Mon, May 18, 2020 at 12:12:24AM +0200, Ludovic Courtès wrote:
>> Hi,
>> 
>> Leo Famulari <leo@famulari.name> skribis:
>> 
>> > On Wed, May 06, 2020 at 06:27:31PM +0200, Vincent Legoll wrote:
>> >> From the manual or from the CI, to let the build farm do more useful things
>> >> I'm not against, but is it really making maintenance difficult by still being in
>> >> the codebase ?
>> >
>> > It's not really a maintenance burden currently since we don't actually
>> > build or maintain the Guix on MIPS at all.
>> >
>> > I think this discussion is evidence that people find the situation a bit
>> > confusing. When I am looking into a project, I find it demotivating to
>> > read documentation about features that may or may not work — it's best
>> > when the documentation accurately reflects what the software can do.
>> 
>> Right, that was my point: let’s remove mentions of MIPS from the manual
>> and from ‘configure.ac’ so people have the right expectations.
>> 
>> Thoughts?
>
> So change it so that mips needs '--with-courage' but not remove the
> bootstrap binaries from the code?

Yes.  (The code has references to those binaries but it no longer has
the binaries themselves.)

> Do we want to fully remove the mention of mips as a supported platform
> or change it to "in the past we had an active mips64el port which is
> in need of more attention to bring it back to a fully supported
> platform. Help wanted!"

Do we really want to call for help in this area?  To me, we just remove
it, and if there’s interest again in this architecture, people might
happily find that part of the work has already been done.

Would you like to send a patch?

Ludo’.


  reply	other threads:[~2020-05-24 21:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 19:32 MIPS support Christopher Baines
2020-04-08 22:07 ` Leo Famulari
2020-05-06 14:39   ` Ludovic Courtès
2020-05-06 16:27     ` Vincent Legoll
2020-05-06 17:35       ` Jack Hill
2020-05-06 17:45       ` Christopher Baines
2020-05-06 18:23       ` Leo Famulari
2020-05-17 22:12         ` Ludovic Courtès
2020-05-18  7:01           ` Efraim Flashner
2020-05-24 21:03             ` Ludovic Courtès [this message]
2020-05-25  9:44               ` Efraim Flashner
2020-05-25 21:20                 ` Ludovic Courtès
2020-05-26  6:15                   ` Efraim Flashner
2020-05-06 18:28       ` Leo Famulari
2020-05-06 22:16         ` Vincent Legoll
2020-05-08 10:55           ` Vincent Legoll
2020-05-26  9:28           ` Christopher Baines

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=87pnatyrji.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=efraim@flashner.co.il \
    --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 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).