Mirror of forum.nim-lang.org

601 :: Babel is now called Nimble

• dom96 (orginal) [2014-10-23T16:38:24+02:00] view original

  Firstly I apologise for such a late announcement. I am now at University so I don't have as much time as I used to. (Thank you lewisl for the constructive criticism!)

  In regards to Nim's official package manager. We decided that it was best to change its name for three reasons:

  • Babel is a common word and is used for other command line applications, one in particular has caused conflict issues for users.
  • To get rid of the biblical connotations which at least one person complained about.
  • Nimrod has been renamed to Nim and the package manager's name no longer had any relation to the language's name.

  So what does this mean? This means that the binary is now called nimble and that packages should use the .nimble extension for their .nimble files (what used to be known as .babel files). The old .babel files will however continue to work for the foreseeable future but you should rename them ASAP.

  There are still documents on github which need to be updated I'm sure and I would appreciate help in fixing them. If you guys have any other questions then please ask them here.

---

• lewisl (orginal) [2014-10-23T18:21:53+02:00] view original

  Thanks.

  Anything special to make sure a package installed by Babel is still accessible to Nim?

  Can those packages be maintained by Nimble? Or should one re-install once the package developer has updated?

---

• dom96 (orginal) [2014-10-24T15:24:18+02:00] view original

  You don't need to do anything special. Nimble will ask you whether you want to move the packages from ~/.babel to ~/.nimble if it detects a ~/.babel directory. The .babel files will be left as-is though. You won't need to reinstall the packages.

---

• exhu (orginal) [2014-11-04T19:56:10+01:00] view original

  tried to remove .babel and cloned nimble from clear start. But it crashes during install

  
  Hint: operation successful (37581 lines compiled; 4.779 sec total; 95.973MB) [SuccessX]
  /home/yur/myprojects/nimble/src/nimble install
  Traceback (most recent call last)
  nimble.nim(810)          nimble
  nimble.nim(196)          parseCmdLine
  json.nim(1395)           parseFile
  json.nim(1364)           parseJson
  json.nim(438)            getTok
  json.nim(342)            skip
  SIGSEGV: Illegal storage access. (Attempt to read from nil?)
  Error: execution of an external program failed
  Run

---

• Araq (orginal) [2014-11-04T22:29:49+01:00] view original

  Which OS, CPU, used C compiler? Which version of Nim(rod)? And please use the bug tracker.

---

• exhu (orginal) [2014-11-05T06:46:34+01:00] view original

  https://github.com/nimrod-code/nimble/issues/65

---

• Stefan_Salewski (orginal) [2014-11-06T14:45:11+01:00] view original

  Just did a clean git install of Nim devel followed by git Nimble.

  But now

  stefan@AMD64X2 ~ $ nimble install c2nim
  Downloading c2nim into /tmp/nimble_2691/c2nim using git...
  Cloning into '/tmp/nimble_2691/c2nim'...
  remote: Counting objects: 35, done.
  remote: Compressing objects: 100% (31/31), done.
  remote: Total 35 (delta 0), reused 24 (delta 0)
  Receiving objects: 100% (35/35), 44.53 KiB | 0 bytes/s, done.
  Checking connectivity... done.
  Installing c2nim-0.9.6
  Building c2nim/c2nim using c backend...
  Hint: used config file '/home/stefan/gitnim/Nimrod/config/nim.cfg' [Conf]
  Hint: system [Processing]
  Hint: c2nim [Processing]
  Hint: strutils [Processing]
  Hint: parseutils [Processing]
  Hint: os [Processing]
  Hint: times [Processing]
  Hint: posix [Processing]
  Hint: parseopt [Processing]
  lib/pure/parseopt.nim(56, 34) Warning: quoteIfContainsWhite is deprecated [Deprecated]
  c2nim.nim(11, 23) Warning: parseopt is deprecated [Deprecated]
  c2nim.nim(11, 33) Error: cannot open 'llstream'
  FAILURE: Execution failed with exit code 1
  
  I have currently no idea what 'llstream' is -- I really think I have removed all old nim related stuff before fresh install today.
  This is Gentoo GNU/Linux AMD64.

---

• Stefan_Salewski (orginal) [2014-11-06T14:51:25+01:00] view original

  I have currently no idea what 'llstream' is

  But Google and Göran do: http://goran.krampe.se/2014/10/16/nim-wrapping-c/

  Thanks, will try to fix it this evening manually.

---