From: grozin@gentoo.org
To: gentoo-lisp@lists.gentoo.org
Subject: Re: [gentoo-lisp] maxima-5.33.0
Date: Tue, 8 Apr 2014 12:01:10 +0700 (NOVT) [thread overview]
Message-ID: <alpine.LFD.2.03.1404081145300.12675@star.inp.nsk.su> (raw)
In-Reply-To: <20140406213848.GA22199@earth.members.linode.com>
On Mon, 7 Apr 2014, Panagiotis Christopoulos wrote:
> could you make a list of the most
> important issues you have related to lisp stuff, that trouble you when working
> with your sci-mathematics packages and reply back here?
I think the current status is OK.
1. gcl
I'd like to remove 2.6.7-r3 (it is masked). I think now it will not
compile without extra patches.
2.6.10 is a good release. When 2.6.11 will appear, I'll add it to the
tree. gcl will support asdf soon (maybe 2.6.11, maybe somewhat later).
When the relevant releases of gcl and asdf will appear, I'll add +asdf USE
flag.
Old versions of gcl were keyworded on many arches; in Debian gcl works on
many arches now. I can only run stuff on ~amd64 and ~x86. Maybe, file a
keywording bug for some arches? Which ones? ppc? ppc64? sparc?
2. clozurecl
There is a keywording bug for ppc and ppc64 filed by Pacho Ramos. If it
will be ever keyworded on ppc, I'll remove the ancient openmcl from the
tree (openmcl was renamed to clozurecl; openmcl in the tree is keyworded
~ppc).
> The lisp team is highly understaffed the last years, we all know about that and
> speaking for myself my free time for Gentoo is very limited but still in this
> mess we have to try making some progress. I believe it's time to put back Lisp
> in staffing needs and try finding new people to recruit.
Yes, this is definitely a good idea.
Best wishes,
Andrey
prev parent reply other threads:[~2014-04-08 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 12:52 [gentoo-lisp] maxima-5.33.0 grozin
2014-04-06 21:38 ` Panagiotis Christopoulos
2014-04-08 5:01 ` grozin [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=alpine.LFD.2.03.1404081145300.12675@star.inp.nsk.su \
--to=grozin@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