Could NimScript (Nimble config file) include a built in test to test if package is installed or local? about nim

[ggb-sw]

OK, I was a little premature in that at least part of the problem (that of having to duplicate code in multiple nimble files) can be mitigated by putting that code in an external include file (which I have also included common tasks - hence why include rather than import).

The issues of portability and future proofing would still exist.

[penguinite]

If you don't mind me asking this, what do you need this for? because there might be a better way to solve your issue, than implementing this.

[ggb-sw]

@penguinite I don't mind you asking at all.

I am writing some code (for my own amusement only) with interdependent modules. Clearly, should I one day decide to release these musings into the wild then the nimble config files should reflect dependencies between the modules, but so long as the modules remain in my own little private zoo of modules then nimble gets confused by references to modules that are not available in the wild. Thus I have to be able to make the dependency references conditional on whether the modules are in my zoo or out in the wild. Thus I am placing lines such as:

if isInstalledPack():
  requires "other_module"

So when running within my zoo, isInstalledPack() returns false and the requires statement is ignored, but if the module is ever released into the wild then isInstalledPack() will return true and nimble knows to download "other_module".