I recommend using atlas. It keeps all your library and dependency locally and 
only update config files.

The way atlas works is that you define a root folder as the basis of the 
workspace and put your dependencies / library on level below it. Atlas will 
generate config file for you that update --path.

Installing dependencies globally is a source of bugs / mistakes IMO.

For example, if i wanted to modify on arraymancer in a new workspace i could do 
:
    
    
    mkdir DevWorkspace
    cd DevWorkspace
    atlas init
    atlas use arraymancer
    
    
    Run

It would clone Arraymancer and all its dependencies in your local workspace 
folder. All the dependencies are git repository that you can modify locally. 
You can inspect the nim.cfg files generated that way to see which --path 
options is used.

Reply via email to