Explicit dependency on uiop for ASDF project using uiop

amoroso

I used SBCL to write a McCLIM program that has an ASDF defsystem definition and calls some uiop functions. Since uiop is part of ASDF, should the dependency of the project on uiop be listed explicitly in the defsystem form?

khinsen

In the same situation, I decided to list it.

For ASDF, it doesn't make a difference. But for human readers, and potentially other tools for system management or documentation, it could be useful to have a complete list of dependecies, including uiop.

crmsnbleyd

I concur, listing it is a sort of documentation, and does not depend on the implementation details of asdf

amoroso

Listing the explicit dependency improves clarity and documentation but may cause conflicts if more than one version of the library is accessible to ASDF, like in my setup which pulls uiop via Lem and Qlot:

* (asdf:locate-system "uiop")
T
NIL
#P"/home/paolo/common-lisp/lem/.qlot/dists/uiop/software/uiop-3.3.7/uiop.asd"
#<ASDF/SYSTEM:SYSTEM "uiop">
0

marcoxa

Extricating UIOP from ASDF would be a Good Thing (tm)

khinsen

ASDF depends on UIOP. Extricating would help only for people who use UIOP but not ASDF.

I tend to see both as de-facto parts of a modern Common Lisp implementation.

marcoxa

khinsen exaclty.