Re: The pkgsrc-2014Q3 Release

["Thomas Mueller" <mueller6724%bellsouth.net@localhost>]

> Getting pkgsrc
==============
> More information can be found in
>         http://www.netbsd.org/docs/pkgsrc/getting.html

> tar files for pkgsrc, along with checksums, can be found at
>         http://ftp.netbsd.org/pub/pkgsrc/pkgsrc-2014Q3/

> and anonymous cvs can be used:
>         cvs -z3 -q -d anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot checkout -r
> pkgsrc-2014Q3 -P pkgsrc

> or by pulling from the git mirrors at:
>         https://github.com/jsonn/pkgsrc
>         https://github.com/joyent/pkgsrc
> or the mercurial mirror at:
>         https://bitbucket.org/agc/pkgsrc.hg

Pkgsrc guide online says nothing about git or mercurial.  I've been using cvs because that's what the guide said, for NetBSD src and pkgsrc trees.

My question is whether there are any special parameters needed to git-clone or pull pkgsrc tree.

Question arises because of problems I've had with haikuports, haikuporter and haikuports.cross from (Atlassian) bitbucket.org relating to (SSL) certificates.

I've never used mercurial (hg), though I recognize the chemical symbol.

Is it better to use git or cvs?  Is git also for NetBSD src trees?

Tom