Wednesday, March 03, 2021

packaging common-lisp programs

Hello,

I'm trying to port an application written in common-lisp, but I'm not
sure how to proceed. The application is tinmop[0], a pleroma and gemini
client.

I ensured that it works^1, and convinced the author to properly tag
releases, but I don't know how to handle quicklisp dependencies.

As far as I can see, the only other common-lisp port is x11/stumpwm and
it gets away with using MASTER_SITES0-2 for its deps. tinmop, on the
other hand, has like 24 dependencies, so it isn't feasible.

What's the best approach in these cases? Hosting a tarball with the
dependencies? Or there are some other tricks to with asdf?

Thanks,

Omar Polo


[0]: https://notabug.org/cage/tinmop.git
[1]: it needs a small patch to revert a commit, because the author is
tracking the master branch of one dependency instead of the stable
release on quicklisp.

No comments:

Post a Comment