all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: brettg@posteo.net
To: John Soo <jsoo1@asu.edu>
Cc: help-guix <help-guix@gnu.org>,
	Help-Guix <help-guix-bounces+brettg=posteo.net@gnu.org>
Subject: ML on Guix (Was: Re: gfortran seems to require gcc-toolchain)
Date: Wed, 20 Nov 2019 06:48:37 +0100	[thread overview]
Message-ID: <001d978bc91768fa4802e0e7b8730ee5@posteo.net> (raw)
In-Reply-To: <C5207F05-BD5B-40E5-B1AC-05F4A3058ACD@asu.edu>



On 20.11.2019 05:37, John Soo wrote:
> Hi Brett,
> 
> A touch off-topic.
> 
>> That is what I do, like in my mlton package.
> 
> Do you have urweb packaged by any chance, too?
> 
> It would really save me the trouble!
> 
> - John

John,

I am familiar with it but I do not have it packaged. If you would like I 
might be able to see if I can do that. I really would like to get the ML 
situation on Guix spiffed up but there are some obstacles that need to 
be addressed (namely around bootstrapping, of course.)

You can reach out to me off list, or on Telegram @brettmg.

Best,
Brett Gilio
https://git.sr.ht/~brettgilio

  reply	other threads:[~2019-11-20  5:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 16:09 gfortran seems to require gcc-toolchain Konrad Hinsen
2019-11-09 23:03 ` Marius Bakke
2019-11-10  7:14   ` Efraim Flashner
2019-11-10 19:50     ` Marius Bakke
2019-11-11 18:08   ` Konrad Hinsen
2019-11-15 17:41     ` Marius Bakke
2019-11-16  8:44       ` Konrad Hinsen
2019-11-18 10:40         ` zimoun
2019-11-18 12:09           ` Konrad Hinsen
2019-11-19 21:26             ` Marius Bakke
2019-11-19 21:28               ` brettg
2019-11-20  4:37                 ` John Soo
2019-11-20  5:48                   ` brettg [this message]
2019-11-30 14:52             ` Konrad Hinsen
2019-11-18 10:43         ` Konrad Hinsen

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=001d978bc91768fa4802e0e7b8730ee5@posteo.net \
    --to=brettg@posteo.net \
    --cc=help-guix-bounces+brettg=posteo.net@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=jsoo1@asu.edu \
    /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.