Open terlar opened 3 years ago
I think it could make a good sense. I'm just wondering how this could work when releasing and when developing. Most of the time, the :extra-paths is a relative path to the project's root directory. So when releasing, would this work? I would assume these extra paths needed to be absolute paths going trough the nix store. I'm also not including the :paths values. If we were to add :paths and :extra-paths, we would be getting closer to a complete clojure runtime wrapper, which we could use to start up a clojure project. Which isn't a bad idea.
It would be nice if
:extra-paths
could be read and populated theextraClasspaths
by default. Right now you have to manually keep those two in sync.If I pass in
extraClasspaths
I would like that to be combined with the:extra-paths
from the aliases. If I have multiple aliases with:extra-paths
and use several of these aliases together with theclj2nix
command I would also expect all of them to be added.What do you think?