1. 27 Mar, 2018 1 commit
    • Kirill Smelkov's avatar
      neotest: v↑ everything · fb5d114a
      Kirill Smelkov authored
      Update verion of lab.nexed.com/kirr/neo.git used and all of its dependencies.
      
      NEO/go now uses 2 Cgo packages:
      
      - github.com/gwenn/gosqlite, and
      - github.com/DataDog/czlib
      
      and github.com/soheilhy/cmux to multiplex NEO & HTTP traffic on the same port.
      
      Otherwise it is straighforward update which transitively pulled some more
      dependencies.
      fb5d114a
  2. 26 Mar, 2018 2 commits
    • Kirill Smelkov's avatar
      golang: Hook-in pkg-config for Cgo support · df7db445
      Kirill Smelkov authored
      The most convenient way to discover CFLAGS/LDFLAGS when building Cgo bits is
      via pkg-config:
      
          https://golang.org/cmd/cgo/
      
      For this to work let's add pkg-config to be available there in gowork out of
      the box, and provide users with a way to specify which C packages they want to
      be there on gowork's $PKG_CONFIG_PATH, e.g. this way:
      
          [gowork]
          cpkgpath =
              ${sqlite3:location}/lib/pkgconfig
              ${zlib:location}/lib/pkgconfig
      
      In buildout sources cpkgpath is specified as multiline - not one line with ":"
      delimiters - with the idea that it should be easy to amend gowork.cpkgpath with "+="
      in different places.
      df7db445
    • Alain Takoudjou's avatar
      use slapos.core version 1.4.5 · 8d623f5f
      Alain Takoudjou authored
      8d623f5f
  3. 25 Mar, 2018 1 commit
  4. 22 Mar, 2018 1 commit
  5. 21 Mar, 2018 3 commits
  6. 20 Mar, 2018 2 commits
    • Boris Kocherov's avatar
      801110bb
    • Jérome Perrin's avatar
      tools: a simple git.mergetool for working with buildout.hash.cfg · 6dbd5cca
      Jérome Perrin authored
      Rewriting commit history with `git rebase -i` always caused some
      conflicts on md5sum of modified files. `update-hash` made all this
      easier, because we could just revert buildout.hash.cfg, re-run
      `update-hash` and commit the changes.
      
      This tool makes this scenario a bit more user friendly by automating the
      steps by running as a git mergetool.
      
      An interactive rebase session can be initiated by running this command
      from software/*/ directory:
      
      `git rebase -i --exec "$(pwd)/../../update-hash $(pwd)/buildout.hash.cfg" origin/master`
      
      and if conflict occur, run:
      
      `git mergetool --tool update-hash-mergetool && EDITOR=cat git rebase --continue`
      
      This way, rebase session can be almost non interactive (still have to
      run the above mergetool command) when conflicts are only on md5sum
      updates.
      
      /reviewed-on nexedi/slapos!273
      6dbd5cca
  7. 19 Mar, 2018 3 commits
  8. 16 Mar, 2018 9 commits
  9. 15 Mar, 2018 5 commits
  10. 14 Mar, 2018 4 commits
  11. 13 Mar, 2018 6 commits
  12. 12 Mar, 2018 3 commits