There is a problem between the ecls ebuild and the cl-ppcre ebuild. Either ecls is not setting virtual/commonlisp or cl-ppcre ebuild doesn't know that ecls is OK. Reproducible: Always Steps to Reproduce: 1. unmerge any common lisp package such as cmucl, sbcl, etc 2. emerge ecls, note that common-lisp controller is installed 3. try emerging cl-ppcre Actual Results: I aborted step 3 and was left with cl-ppcre uninstalled :( Expected Results: should have known that ecls is a common-lisp, and that it works fine with cl-ppcre thanks for providing common lisp ebuilds
Greetings The Janitor. ECL doesn't export virtual/commonlisp because it really hasn't been tested against compiling and running all other other cl-* packages in dev-lisp/ yet. This bug is related to Bug #86056. All thats required is a some files for the common lisp controller.
In dev-lisp/ecls-0.9f_p1, I added a minimal support for "the common lisp controller". Actually, its a hacked down, minimal controller which adds /usr/share/common-lisp/systems/ to ASDF:*CENTRAL-REGISTRY* and extends the ASDF:OUTPUT-FILES method to place FASLs in /var/cache/common-lisp-controller/<userid>/ecl/. See the README.Gentoo. http://www.gentoo.org/cgi-bin/viewcvs.cgi/dev-lisp/ecls/files/clc-lite.lisp?view=markup http://www.gentoo.org/cgi-bin/viewcvs.cgi/dev-lisp/ecls/files/README.Gentoo?view=markup