I am in the design phase of building a deployment tool for CL projects.
I imagine the typical workflow to be like so:
(ql:quickload :yolo)
(yolo:configure)
- Developer adds remote machine user and host, etc...
- Developer goes to bed. Turns off the PC
- In the morning: hack hack hack
- Time to deploy. Developer commits changes and goes to the REPL and types
(yolo:deploy)
What I want is for my library to know which system the developer wants deployed based on the current package. (*package*
)
My question: Is it possible to find the system that loaded a particular package? Naturally I am talking about ASDF
.
Bonus question: Is such a tool even needed? Perhaps there is a better workflow. I am also planning to make the library an executable, but then the default project can be obtain by the current directory.
First, read about packages, systems, libraries etc. here.
I do not think that it makes much sense to infer the intended system. You need at least one additional parameter anyway (the target where to deploy).
A few ideas:
I imagine that a deployment tool would deploy a system. It would then perhaps sensibly be defined as an extension for ASDF.
For example, you might devise such an extension so that you can specify deployment configuration in the
defsystem
form like this:This information could then be used in a new op
deploy-op
, that you might invoke like: