Ivan Yonchovski

@arnetheduck compiler ATM has only the sources. I am adding the binaries as well + pretty much the content of the nimlang tar delivery.

> presumably because it lives in the same directory? It is due to this line: https://github.com/nim-lang/Nim/blob/devel/compiler.nimble#L7 There is also `nimsuggest.nimble` so I suspect that the idea was to have it...

Hey @Araq , can you take a look? Based on our previous conversion I believe that you don't want to structure the repo in a way to make it "nimble...

I am fine with using json. Something like that: ``` json { "name": "foobar", "version": ">= 1.0", "resolvedTo": "1.1", "depedencies": [{ "name": "foobar-dep", "version": ">= 1.0", "resolvedTo": "1.1", "error": "xx",...

@Araq WDYT about @zah's proposal: having the human-readable format as default and then at some point add machine-readable (json). ATM it seems like the primary use case is to run...

@dom96 it won't be simply putting the functions into a separate module - that would require restructuring the whole file. `deps` functionality uses `processFreeDependencies` which is nimble.nim which then uses...

I can put depsRecursive and printDepsHumanReadable

> Seems fair. Though can you elaborate what will end up in the lock file when `nimble lock` is called? Here is what it looks like(I have patched packages.json locally...

@dom96 please disregard this PR - refer to https://github.com/nim-lang/Nim/pull/20179#issuecomment-1209010294 I have to revisit the implementation.

@dom96 applied your comments(hopefully I haven't missed anything).