all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: paren@disroot.org, Jon Eskin <eskinjp@gmail.com>,
	jgart@dismail.de, 55151@debbugs.gnu.org, 53833@debbugs.gnu.org
Subject: [bug#53833] [PATCH] gnu: Add qbe.
Date: Mon, 02 May 2022 08:33:22 +0200	[thread overview]
Message-ID: <23ff4ecaf07b3cec38d452d69785f1dd450581d7.camel@ist.tugraz.at> (raw)
In-Reply-To: <87h7694cma.fsf@gnu.org>

Hi Ludo,

Am Sonntag, dem 01.05.2022 um 15:16 +0200 schrieb Ludovic Courtès:
> Hi,
> 
> Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> skribis:
> 
> > Am Montag, dem 25.04.2022 um 20:05 +0000 schrieb paren@disroot.org:
> > 
> > > QBE is now being used in one reasonably mature project:
> > > https://harelang.org
> > > 
> > > While it's not at 1.0 yet, it's been in development for ~2 (i
> > > think) years now.
> > I'm not asking for a 1.0, I'd be fine with a 0.1 or even a 0.0.1. 
> > As it stands, every place I look at says "this is experimental"
> > rather than "you can use this and it ought to work as intended at
> > least for these sample programs".
> 
> But that’s fine: having a web page at all, or one that doesn’t read
> “experimental”, has never been a criterion for getting a package in
> Guix.
That's not my criterion either.  My critierion is more or less "Will we
have to revision-bump this package daily/every few days because people
want to play with the latest stuff?"  With upstream having seen no
commit for three weeks at this point, I guess it might be fine.

> There’s now a second patch for qbe:
> 
>   https://issues.guix.gnu.org/55151
> 
> I propose to go ahead and apply it, adding anything missing from
> paren’s initial patch.
IMHO, paren's initial patch is slightly better in quality than 55151,
but there are two (three) things lacking.  First, the synopsis and
description are subpar.  55151 has a slightly better synopsis, don't
feel too sure about the description though.  Second, the "fix-cc" phase
from 55151 should be added after unpack ("patch-test-script" sounds
like a better phase name).  It might be better to use (cc-for-target)
in the substitution rather than gcc, but note that this substitution
only applies for native compilation anyway.

cproc too seems to grow at a slower pace now.  Might be worth moving
stuff over from guixrus now.  Note that the cproc package has #:tests
#f without an explanation, though, so it needs some polishing.

Cheers




  reply	other threads:[~2022-05-02  6:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <454d4c514fc4485670cf8f2ec891034c9014edc0@disroot.org>
2022-04-26  7:43 ` [bug#53833] [PATCH] gnu: Add qbe Liliana Marie Prikler
2022-05-01 13:16   ` Ludovic Courtès
2022-05-02  6:33     ` Liliana Marie Prikler [this message]
2022-02-07  1:13 jgart via Guix-patches via
2022-02-07  9:47 ` Liliana Marie Prikler
2022-02-08 21:10   ` jgart via Guix-patches via
2022-04-25 20:08 ` paren--- via Guix-patches via
2022-04-26 18:16 ` paren--- via Guix-patches via
2022-05-07 17:09 ` (unmatched-parenthesis via Guix-patches via

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=23ff4ecaf07b3cec38d452d69785f1dd450581d7.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=53833@debbugs.gnu.org \
    --cc=55151@debbugs.gnu.org \
    --cc=eskinjp@gmail.com \
    --cc=jgart@dismail.de \
    --cc=ludo@gnu.org \
    --cc=paren@disroot.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.