Why use Quicklisp in CI?

atlas-engineer / nfiles

User configuration and data file management

BSD 3-Clause "New" or "Revised" License

17 stars 5 forks source link

Closed Ambrevar closed 1 year ago

Ambrevar commented 1 year ago

@aartaka https://github.com/atlas-engineer/nfiles/actions/runs/3409258951/jobs/5670800095 fails because (asdf:system-relative-pathname :nfiles "test-data") does not work. Indeed, the CI uses Quicklisp and not ASDF.

Was it a deliberate choice? Why not work like Nyxt which has been working reliable without Quicklisp so far?

aartaka commented 1 year ago

Because ASDF comes together with submodules, and we don't use submodules in most libraries we use. See https://github.com/atlas-engineer/ntemplate/issues/5

aartaka commented 1 year ago

But wait, does Quicklisp not use ASDF underneath?

Ambrevar commented 1 year ago

Yup, but as you can see, not properly enough :(

Why not use submodules for libraries?

It would make them reproducible.
It pins the commits, which is good practice. (Kind of the same, but good to emphasize.)
Removes dependency on Quicklisp.
Does not require HTTP (unencrypted) like Quicklisp.

Ambrevar commented 1 year ago

See #11.