Replies: 1 comment
-
@eadlam - great question. @rogpeppe and I were just discussing your situation. There are lots of possibilities/options, it really rather depends on what it is you are trying to do. As such, jumping onto a call is likely going be the most efficient way of helping improve our understanding, but also sharing with you the option space. We can then do a short write-up in this discussion for the benefit of others following along. Please feel free to drop me an email paul@cue.works to get something scheduled if that works for you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm delivering an SDK to end users which includes a lot of cue modules. This currently works ok by copying
cue.mod/pkg
into new projects. It would be better if they could be installed into a common system directory. It is not ideal for these to be fetched from a registry or to make the user run a local registry. Will the old style modules continue to be supported and has there been any more discussion around file system module management?Beta Was this translation helpful? Give feedback.
All reactions