From: Stelian Ionescu <sionescu@cddr.org>
To: gentoo-lisp@lists.gentoo.org
Subject: Re: [gentoo-lisp] common lisps overlay -> tree; maxima, fricas
Date: Sat, 20 Apr 2013 20:53:03 +0200 [thread overview]
Message-ID: <1366483983.4518.17.camel@cathai> (raw)
In-Reply-To: <alpine.LNX.2.00.1304202156050.27173@elrond.inp.nsk.su>
[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]
On Sat, 2013-04-20 at 22:13 +0700, grozin@gentoo.org wrote:
> 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).
clozurecl-1.9-r3 is not a live ebuild, what makes you think that ?
Please don't put snapshots in portage unless really necessary, and this
is not the case since upstream makes regular releases.
> 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.
What are you unsure about ?
--
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
http://common-lisp.net/project/iolib
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-20 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 15:13 [gentoo-lisp] common lisps overlay -> tree; maxima, fricas grozin
2013-04-20 18:53 ` Stelian Ionescu [this message]
2013-04-21 2:49 ` A.G.Grozin
2013-04-21 10:52 ` Stelian Ionescu
2013-04-22 7:11 ` A.G.Grozin
2013-04-22 12:33 ` Stelian Ionescu
2013-04-24 14:10 ` A.G.Grozin
-- strict thread matches above, loose matches on Subject: below --
2013-04-24 14:57 grozin
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=1366483983.4518.17.camel@cathai \
--to=sionescu@cddr.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