The macro was using a gensym for the target resource path, but
something in the hook system does some mangling of the arguments into
keyword arguments with magic names, so to actually get the target into
the hook properly it has to be named with the particular symbol
directory.
Right. I think the hook system worked differently at one point during development and it slipped my mind to fix this up when I changed it. Sorry for the trouble.
The macro was using a
gensym
for the target resource path, but something in the hook system does some mangling of the arguments into keyword arguments with magic names, so to actually get the target into the hook properly it has to be named with the particular symboldirectory
.see https://github.com/Shinmera/deploy/issues/1