On Wed, Mar 03, 2021 at 04:24:46PM +0100, Omar Polo wrote: > 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
Other reasonable languages tend to actually have dependencies, like separate ports. If you don't have anything to package, you can always use the lesser known features of BUILD_DEPENDS See bsd.port.mk(5).... you will probably find BUILD_DEPENDS = some/path:patch to be more or less what you would need.
