Basically I want to reuse several very small utilities I wrote. Till recently I used (possibly misused) "nimble develop" on a single package containing the various files. This has been serviceable so far, but always felt like I don't really know what's happening. To change that I tried to read the documentation for nimble, but honestly, even after several times reading through it, I don't think I understand more. didn't get far.
For example
..code-block: bash
nimble develop --remove-path somePath
fails with "Error: Unknown option: --remove-path". Using nimble v0.13.1 and nim 1.6.0, not sure what else could affect it.
So, now my questions are:
If yes to all of the above, is there a much simpler tutorial/guide/example for how to manage sources locally? Otherwise, what is the recommended way to organize source code?
The docs at https://github.com/nim-lang/nimble are for the latest Nimble version (0.14.0) which hasn't been released yet. You may wish to look at the 0.13.1 docs specifically via: https://github.com/nim-lang/nimble/tree/v0.13.1#nimble-develop.
Can you elaborate on what you're trying to do? Are you developing libraries or apps?
Ouch, that explains those discrepancies. Thanks, I'll have a look if those clear up my issues.
Well, while learning about nim I wrote small programs. Some I like to reuse in other programs, also mostly motivated by learning about something. The most convenient way I found so far is organizing them into one package and using "nimble develop". But now I'd like to actually know and understand what is involved.
Does it make sense to wait for the release of 0.14.0? A quick scan of the 0.13.1 docu gives me the impression there are many changes.
So far, I'd say a plain "nimble install" (run in the local package's directory) does what I originally wanted.
I probably should have used "nimble uninstall myLocalPackage" to undo "nimble develop". After I did, "nimble install" behaved as expected.