Mirror of forum.nim-lang.org

1098 :: Nimble install global vs. local

• Orion (orginal) [2015-04-02T18:39:19+02:00] view original

  It would be nice if nimble handled things more like nuget or npm, where when you install a directory or attempt to resolve dependencies, they are resolved locally in the project rather than globally ( ./.nimble instead of ~/.nimble directory), and add it to a gitignore automatically

---

• dom96 (orginal) [2015-04-03T12:35:28+02:00] view original

  There will be a global vs. local distinction when installing packages, but the distinction won't be as you describe it. Global will install for all users under /usr/lib/nimble (on Linux at least) and local will install in ~/.nimble.

---

• hakand (orginal) [2015-04-03T13:28:57+02:00] view original

  re dom96:

  Many languages uses some kind of local install per project mechanism, as different projects may use different versions of the same lib (python virtual env, or npm/nuget installing to project directory etc.).

  Not a problem for now considering the low number of libs/packages, but we may need that functionality in the future?

---

• dom96 (orginal) [2015-04-03T15:03:34+02:00] view original

  @hakand that is not a problem with nimble currently

---

• Orion (orginal) [2015-04-07T23:18:39+02:00] view original

  dom96 it is a problem for projects that aren't on nimble but use nimble projects.

  For example

  1. Joe likes building web apps for fun he creates a new project called "MyProject1"
  2. Joe calls nimble install jester in MyProject1
  3. dom96 updates jester and it breaks compatibility in some way
  4. 2 months go by, Joe builds a new web app called "MyProject2"
  5. Joe calls nimble install jester, jester is updated to the latest and greatest

  Joe builds "MyProject2" against the latest jester, but now if he wants to go back and fix a bug in "MyProject1" suddenly nothing builds.

---

• Jehan (orginal) [2015-04-08T07:54:52+02:00] view original

  I concur with Orion. You really want a commandline option or environment variable in order to set the nimble path so that upgrades don't randomly break stuff. At least that's what years of experience with Python have taught me.

---

• andrea (orginal) [2015-04-10T15:20:06+02:00] view original

  I also would like to see this in nimble. Being able to scope dependencies to a single project is one of the things I miss most from Scala

---

• dom96 (orginal) [2015-04-10T22:18:11+02:00] view original

  @Orion Joe will still be able to build it by using nimble build in the MyProject1 directory. I think we should embrace this and provide nimble c file.nim.

---