Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-lisp
Lists: gentoo-lisp: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-lisp@g.o
From: Marijn <hkBst@g.o>
Subject: Re: importing asdf-2 to the main tree?
Date: Wed, 02 May 2012 09:50:34 +0200
Hash: SHA1

On 01-05-12 18:38, Andrey G. Grozin wrote:
> Hello *,
> Currently there is a bug #411453 which hits many users. The most 
> reasonable thing to do is to have asdf-2.x in the main tree (the
> latest version is 2.21, as far as I know). This will allow us to
> import the newest cmucl to the main tree, too.
> The current asdf ebuild in the lisp overlay imports 
> common-lisp-3.eclass. Could somebody import it to the main tree?
> This requires a discussion at gentoo-dev, of course. But, I think,
> we really need to have a (more or less) current asdf in the tree.
> Andrey

Hi Andrey,

according to a conversation on 27 March in #gentoo-lisp with Stelian
(fe[nl]ix) that new eclass is not suitable for review and needs a
rewrite. This was discussed in the context of bumping SBCL which
neurogeek has been working on. Stelian remarked that SBCL for main
tree can depend on gentoo-init-0.1 which depends on older versions of
asdf. The same would prolly work for CMUCL.

This is not a perfect solution, but would allow bumping CMUCL without
worrying about asdf-2 for now... Getting current asdf in main tree is
prolly the longer term solution.


Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


importing asdf-2 to the main tree?
-- Andrey G. Grozin
Lists: gentoo-lisp: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
importing asdf-2 to the main tree?
Previous by date:
importing asdf-2 to the main tree?

Updated May 02, 2012

Summary: Archive of the gentoo-lisp mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.