unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: "Bonface M. K." <bonfacemunyoki@gmail.com>
Cc: guix-devel@gnu.org, Dimos Dimakakos <me@bendersteed.tech>
Subject: Re: Racket packages / build system
Date: Tue, 20 Oct 2020 20:49:57 -0400	[thread overview]
Message-ID: <87imb4o11m.fsf@dustycloud.org> (raw)
In-Reply-To: <86eelu3x7v.fsf@gmail.com>

Bonface M. K. writes:

> Christopher Lemmer Webber <cwebber@dustycloud.org>
> writes:
>
> [...]
>
>>> Can I volunteer on this task? There's some work in
>>> my team done in Racket; and it would be of great
>>> interest to us to have a working Racket build
>>> system. I can set apart some time to work on
>>> this. I'd ask for alot of guidance/ review on this
>>> though :)
>>
>> YES!  Please do.  Let's talk.  You can ping me on IRC also, dustyweb on
>> freenode.
>>
>
> Thanks! I'm called bonz060 on FreeNode; though nowadays I've
> grown to be an e-mail person.
>
> [...]
>
>>> Please do share the notes! I can try to hack
>>> something up \m/\m/.
>>
>> I looked at the email that Dimos sent to me (also the email I had was
>> apparently not the most recent email that they are using, corrected in
>> the addressing this time), and they had asked me if they should post it
>> to the mailing list, so I think that's consent to post it since they
>> expressed consideration in doing so in our exchange... so I'm attaching
>> it.
>>
>
> [...]
>
> Thanks for the notes. I've skimmed through them
> and they seem sensible. I'll look at how other
> build systems are written as a first step, then
> get my hands wet.
>
> Do I open an issue for this---I can't see anything
> that tracks this even in archived issues--- then
> send patches there? Or do I send patches off the
> list and then submit the final drafts(if we get
> there) on the list later?

That sounds like a great plan!


  reply	other threads:[~2020-10-21  0:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-17 18:42 Racket will move on top of Chez soon Christopher Lemmer Webber
2020-10-17 19:14 ` Pierre Neidhardt
2020-10-18 13:06 ` Bonface M. K.
2020-10-19  4:53   ` Racket packages / build system Christopher Lemmer Webber
2020-10-19 10:09     ` Bonface M. K.
2020-10-19 17:04       ` Christopher Lemmer Webber
2020-10-19 17:13         ` Dimos Dimakakos
2020-10-19 18:08         ` Bonface M. K.
2020-10-21  0:49           ` Christopher Lemmer Webber [this message]
2020-10-21 10:33           ` Ludovic Courtès
2020-10-21 12:59             ` Bonface M. K.
2021-01-28  3:03           ` Stephen Paul Weber
2020-11-09 20:54     ` Bonface M. K.
2020-11-09 21:21       ` Dimos Dimakakos
2020-11-09 22:51         ` Christopher Lemmer Webber
2020-11-10 12:07           ` Bonface M. K.
2020-11-10 17:37             ` Christopher Lemmer Webber
2020-11-11 10:53               ` Bonface M. K.
2020-11-10 12:30           ` Bonface M. K.

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=87imb4o11m.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=bonfacemunyoki@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=me@bendersteed.tech \
    /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).