From: grozin@gentoo.org
To: gentoo-lisp@lists.gentoo.org
Cc: gentoo-science@lists.gentoo.org
Subject: [gentoo-science] common lisps overlay -> tree; maxima, fricas
Date: Sat, 20 Apr 2013 22:13:46 +0700 (NOVT) [thread overview]
Message-ID: <alpine.LNX.2.00.1304202156050.27173@elrond.inp.nsk.su> (raw)
Hello *,
Today I've committed to the tree the following packages (all pmasked):
dev-lisp/asdf-2.33-r4
dev-lisp/uiop-2.33-r1
dev-lisp/sbcl-1.1.6-r4
dev-lisp/clisp-2.49-r7.ebuild
dev-lisp/clozurecl-1.9_p1
dev-lisp/ecls-12.12.1-r4
dev-lisp/cmucl-20d-r3
sci-mathematics/maxima-5.30.0
sci-mathematics/fricas-1.2.0
The lisp stuff is from the lisp overlay. I haven't used the overlay
specific eclasses, just the standard helpers (doins etc.).
clozurecl-1.9-r3 from the overlay is a live ebuild; are some of the recent
updates essential? I replaced it by the today's snapshot (I've put it to
dev.gentoo.org).
In clisp, I've corrected the dependency on pari (alas, it has to be
<pari-2.5), and added an upstream patch which may be needed for new gcc
versions.
All abuilds are EAPI=5. Now, when a lisp used for maxima or fricas is
upgraded, these CASs will be upgraded automatically - this is exactly the
main point of EAPI5. It would be great to unmask all these packages soon,
not to wait for years. Any specific reasons not to do so for any of these
packages? Should something be improved before unmasking? Please, test! And
inform me. Testsuites of maxima and fricas are OK, so, the lisps cannot be
broken. But I am not so sure about the asdf stuff.
Andrey
next reply other threads:[~2013-04-20 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 15:13 grozin [this message]
2013-04-22 3:26 ` [gentoo-science] common lisps overlay -> tree; maxima, fricas Steven Trogdon
2013-04-29 21:50 ` fbissey
2013-04-30 16:13 ` grozin
2013-04-30 18:55 ` Francois Bissey
2013-05-23 10:22 ` fbissey
2013-05-23 21:38 ` fbissey
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.LNX.2.00.1304202156050.27173@elrond.inp.nsk.su \
--to=grozin@gentoo.org \
--cc=gentoo-lisp@lists.gentoo.org \
--cc=gentoo-science@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