Closed kloetzl closed 5 years ago
Thanks for your help! I've had strange issues like this before, but I have been able to patch them up with some work. I'll get back to you upon its resolution.
The design decision of providing local builds of dependencies is to avoid requiring system-wide installation and associated sudo privileges. Additionally, this way I can ensure that recent versions are being used. (For example, if you want to use gzbuffer
, you need zlib >= 1.2.6, which is not installed by default on many operating systems.) It does come with various hassles, but I think that making it relatively easy for local builds makes it an overall win.
Perhaps including frozen copies of these dependencies instead of submodules may be a better solution, eliminating potential issues with upstream git history revisions.
Perhaps including frozen copies of these dependencies instead of submodules may be a better solution, …
In Debian that is called a “convenience copy” and is explicitly forbidden by the policy. That prevents dashing from entering the Debian package repositories.
As of the latest version checkout works fine now. However git status
produces a new error message:
fatal: not a git repository: cppitertools/../../.git/modules/bonsai/modules/cppitertools
fatal: 'git status --porcelain=2' failed in submodule bonsai
Looks fixed in v0.1.1-27-g784609b.
As mentioned in the readme I did a
git clone --recursive https://github.com/dnbaker/dashing
which downloaded a bunch of stuff but then ended withApart from the error I am wondering why dashing/bonsai comes with copies of zlib, zstd, divsufsort and others at all? My computer has perfectly fine versions of them installed already.