From: Akater <nuclearspace@gmail.com>
To: Crystalsun <crystalsun@protonmail.com>,
"gentoo-lisp\@lists.gentoo.org" <gentoo-lisp@lists.gentoo.org>
Subject: Re: [gentoo-lisp] Emerge in Common Lisp
Date: Mon, 26 Feb 2018 09:55:56 +0000 [thread overview]
Message-ID: <87y3jgrs5v.fsf@gmail.com> (raw)
In-Reply-To: <hh2uCmTwX_MqF_ju-lNvYpIejRNzZNWP00CBI7UMeogspUegX36v3W4VVv4i93r_d5UycHHGTIcGXD53WMjDcbdoQvTU6c2NRqc_3HwmDC0=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
Crystalsun <crystalsun@protonmail.com> writes:
> Anyone thought about implementing Emerge in Common Lisp?
I did. I know some other people did, too.
> I guess it could be useful due to the interactiveness Common Lisp
> provides
Agree.
> if emerge was written in Common Lisp, it could be possible to
> interactively debug the error and continue the process
Not neccesarily. ebuilds are still ebuilds, namely Unix shell
scripts. Most of my problems come from them not from emerge per se.
> I know it may sound ambitious
It does.
> but at least it seems like an interesting idea to me, would be great
> if anyone has thoughts on this topic
Portage is updated regularly. EAPI evolves. Try estimating how many
man-hours are put into it. That will give you some perspective on
man-hours needed to maintain another implementation. Make some research
on existing attempts (Paludis).
The most promising way in my amateur-ish opinion would be to localise
some task which Portage is slow at, and try to reimplement it (100%
correctly!) for immediate and hopefully long-lasting gains. At least
that could provide the project with some momentum and attention early
on.
Another attractive goal would be the ability to resolve
dependencies interactively. I'm not even where to start with this
though. Maybe if user could increase the backtracking threshold
(emerge --backtrack=n) without restarting the whole thing, that would
already be worth it, who knows. That would require lazy search of some
kind.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2018-02-26 9:59 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 [this message]
2018-02-27 19:01 ` Chema Alonso
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=87y3jgrs5v.fsf@gmail.com \
--to=nuclearspace@gmail.com \
--cc=crystalsun@protonmail.com \
--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