From: Chema Alonso <nimiux@gentoo.org>
To: gentoo-lisp@lists.gentoo.org
Subject: Re: [gentoo-lisp] Emerge in Common Lisp
Date: Tue, 27 Feb 2018 19:01:19 +0000 [thread overview]
Message-ID: <20180227190119.GA8533@woodpecker.gentoo.org> (raw)
In-Reply-To: <hh2uCmTwX_MqF_ju-lNvYpIejRNzZNWP00CBI7UMeogspUegX36v3W4VVv4i93r_d5UycHHGTIcGXD53WMjDcbdoQvTU6c2NRqc_3HwmDC0=@protonmail.com>
Sounds amazing, unfortunatelly we lack the manpower to get to it.
You can always open a bug at bugzilla [1] to ask for this new package
and track its development in case it occurs one day.
In this case, please reply to this message with the bug number and
I'll assign it to the Common Lisp project.
Thanks for your contribution.
Regards.
[1] https://bugs.gentoo.org/
On Sun, Feb 25, 2018 at 09:05:11AM -0500, Crystalsun wrote:
> Anyone thought about implementing Emerge in Common Lisp?
> I guess it could be useful due to the interactiveness Common Lisp provides, and Python doesn't (at least not enough of it). For example, when emerging a package, if an error occures, the whole process will die since the merge of the current atom. However, if emerge was written in Common Lisp, it could be possible to interactively debug the error and continue the process, which, overall, means more user control of what's happening and better hotfixes, thanks to the fact that REPL is part of the language.
> I know it may sound ambitious, but at least it seems like an interesting idea to me, would be great if anyone has thoughts on this topic
prev parent reply other threads:[~2018-02-27 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 14:05 [gentoo-lisp] Emerge in Common Lisp Crystalsun
2018-02-26 9:55 ` Akater
2018-02-27 19:01 ` Chema Alonso [this message]
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=20180227190119.GA8533@woodpecker.gentoo.org \
--to=nimiux@gentoo.org \
--cc=gentoo-lisp@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox