Failed to build for Quicklisp dist about bdef HOT 4 CLOSED

I thought you skip systems with missing dependencies? Incudine is not in Quicklisp, so it is expected that the bdef/incudine sub-system will not build unless Incudine is manually included in one's local-projects directory.

The same is true for defaultxr/cl-patterns#10 ; these failures are caused by systems not yet in Quicklisp, which need to be downloaded manually.

If missing dependencies now cause failures in Quicklisp, is there a way to denote a system as an "expected failure" or otherwise have Quicklisp ignore it? Do these kinds of systems need to be moved out to their own separate .asd file?

from bdef.

from bdef.

For now I think it would be best to just exclude the failing systems for bdef and cl-patterns, as I'm not sure the cl-alsaseq dependency would meet all of Quicklisp's requirements yet (I haven't checked, it might throw warnings).

I'm also not really involved in the development of incudine, I just depend on it, so I can't really say anything about if that one is Quicklisp-ready, or if the author is even interested in it being on Quicklisp.

from bdef.

Thanks, I'll excluded these systems from builds and build failure reports.

from bdef.