| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 01-05-12 18:38, Andrey G. Grozin wrote: |
| 5 |
> Hello *, |
| 6 |
> |
| 7 |
> Currently there is a bug #411453 which hits many users. The most |
| 8 |
> reasonable thing to do is to have asdf-2.x in the main tree (the |
| 9 |
> latest version is 2.21, as far as I know). This will allow us to |
| 10 |
> import the newest cmucl to the main tree, too. |
| 11 |
> |
| 12 |
> The current asdf ebuild in the lisp overlay imports |
| 13 |
> common-lisp-3.eclass. Could somebody import it to the main tree? |
| 14 |
> This requires a discussion at gentoo-dev, of course. But, I think, |
| 15 |
> we really need to have a (more or less) current asdf in the tree. |
| 16 |
> |
| 17 |
> Andrey |
| 18 |
|
| 19 |
Hi Andrey, |
| 20 |
|
| 21 |
according to a conversation on 27 March in #gentoo-lisp with Stelian |
| 22 |
(fe[nl]ix) that new eclass is not suitable for review and needs a |
| 23 |
rewrite. This was discussed in the context of bumping SBCL which |
| 24 |
neurogeek has been working on. Stelian remarked that SBCL for main |
| 25 |
tree can depend on gentoo-init-0.1 which depends on older versions of |
| 26 |
asdf. The same would prolly work for CMUCL. |
| 27 |
|
| 28 |
This is not a perfect solution, but would allow bumping CMUCL without |
| 29 |
worrying about asdf-2 for now... Getting current asdf in main tree is |
| 30 |
prolly the longer term solution. |
| 31 |
|
| 32 |
Marijn |
| 33 |
|
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 36 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 37 |
|
| 38 |
iEYEARECAAYFAk+g50oACgkQp/VmCx0OL2yQhQCgoTwinwmkJP8vZGWf9OyVbWYu |
| 39 |
ANAAoJYG+GxxkC9ttAAlFzQYl1kVXkeB |
| 40 |
=R+2D |
| 41 |
-----END PGP SIGNATURE----- |
Archives