I am close to being able to publish yet another graphical interface module for nim. It will sit on top of oldwinapi or gtk2 and be philosophically similar to iup. I am currently developing it (on Ubuntu) using a local GIT repository which is in my working directory and pushing versions of the module using nimble install so they end up in my user's home .nimble directory.
Once I publish this (hopefully on Github), how do I keep the nimble package separate from the development respository - so the module can be used without needing to dig through the development files.
Pointers to tutorials on publishing nim modules would be appreciated as I have not published software before.
It's a little difficult to understand your directory structure.
If you've got a monorepo then you can publish multiple Nimble packages in that repo. You just use a URL like this: https://github.com/nimble-test/multi?subdir=alpha (this is an example of a monorepo, and Nimble will install a package from the alpha subdirectory with that url).
Otherwise I need more info to help you.
@dom96 How would you set things up if project ''beta'' depends on ''alpha'' ? Trying to understand what is the best practice to develop both projects at the same time.
Thanks!