From: Peter C. <pc...@ma...> - 2013-11-22 10:28:43
|
On Wed, Nov 20, 2013 at 11:19:16AM +0000, John Marshall wrote: > That is the current default place for it; probably the only thing you > were missing, as Rob noted, is that currently you need the develop > branch of htslib too. That was indeed correct. Thank you both very much. > I've now made develop the default branch for htslib too, so you'll get > the current code by default in future git clones. Apologies for the > confusion. This also worked, although it wasn't obvious to me at first. The correct code was checked out and the compilation went smoothly, but in git the remote branch being tracked was not "develop", but instead "bcftools+calling": $ git clone https://github.com/samtools/htslib.git Cloning into 'htslib'... ... $ cd htslib/ $ git branch * bcftools+calling It turns out that at this moment, the "develop" and "bcftools+calling" branch point to the same commit (as determined by git ls-remote). Presumably, once they diverge, new clones will automatically follow "develop", as intended. In the meantime, in order to follow the latest (unstable) development, one should use the syntax Rob suggested earlier: $ git clone -b develop https://github.com/samtools/htslib.git Or "git checkout develop" after cloning. Thanks again for your insight, your timely fix, and your continuing work on this fundamental software. --Peter |