From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: jgart <jgart@dismail.de>, Guix Help <help-guix@gnu.org>
Subject: Re: Erlang Development with Guix
Date: Thu, 30 Jun 2022 11:00:03 +0200 [thread overview]
Message-ID: <b1bf6670-e2f0-b551-4491-e16d82d5d70b@crazy-compilers.com> (raw)
In-Reply-To: <20220629202745.GC1909@gac>
Am 30.06.22 um 03:27 schrieb jgart:
> Is there a guide that shows the particularities of using erlang with
> guix for development, or a mailing list thread I can read?
The rebar-build-system I created was published just a few weeks ago.
Anyhow, I'm not a Erlang/OTP user, so this build-system might still need
improvement. Any help on this is welcome.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2022-06-30 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 1:27 Erlang Development with Guix jgart
2022-06-30 9:00 ` Hartmut Goebel [this message]
2022-10-12 3:13 ` jgart
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=b1bf6670-e2f0-b551-4491-e16d82d5d70b@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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.
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).