$ cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r pkgsrc-20xxQy -P pkgsrc +

$ cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r pkgsrc-2017Q3 -P pkgsrc

Where pkgsrc-20xxQy is the stable - branch to be checked out, for example, “pkgsrc-2016Q4”

This will create the directory pkgsrc/ in your /usr/ directory and all the package source will be stored under /usr/pkgsrc/.

@@ -1062,7 +1057,7 @@ release -d by adding the option “-A” after the “update” keyword. To switch from the current branch back to the stable branch, add the - “-rpkgsrc-2016Q4” option.

+ “-rpkgsrc-2017Q3” option.

@@ -8840,7 +8835,7 @@ place.
and if you still don't have the answer, ask on the `pkgsrc-users` mailing list.

-
+

22.1. What is the difference between MAKEFLAGS, .MAKEFLAGS and MAKE_FLAGS? @@ -8885,7 +8880,7 @@ do? -
22.1.
+
22.1.

What is the difference between `MAKEFLAGS`, `.MAKEFLAGS` and @@ -8901,7 +8896,7 @@ do? -
22.2.
+
22.2.

What is the difference between `MAKE`, `GMAKE` and @@ -8919,7 +8914,7 @@ do? -
22.3.
+
22.3.

What is the difference between `CC`, `PKG_CC` and @@ -8937,7 +8932,7 @@ do? -
22.4.
+
22.4.

What is the difference between `BUILDLINK_LDFLAGS`, @@ -8950,7 +8945,7 @@ do? -
22.5.
+
22.5.

Why does make show-var VARNAME=BUILDLINK_PREFIX.`foo` @@ -8966,7 +8961,7 @@ do? -
22.6.
+
22.6.

What does `${MASTER_SITE_SOURCEFORGE:=package/}` mean? I @@ -8990,7 +8985,7 @@ do? -
22.7.
+
22.7.

Which mailing lists are there for package developers?
@@ -9015,7 +9010,7 @@ do? -
22.8.
+
22.8.

Where is the pkgsrc documentation?
@@ -9063,7 +9058,7 @@ do? -
22.9.
+
22.9.

I have a little time to kill. What shall I do?
Index: pkgsrc/doc/pkgsrc.txt diff -u pkgsrc/doc/pkgsrc.txt:1.244 pkgsrc/doc/pkgsrc.txt:1.245 --- pkgsrc/doc/pkgsrc.txt:1.244 Sun Nov 26 09:43:17 2017 +++ pkgsrc/doc/pkgsrc.txt Mon Nov 27 11:52:49 2017 @@ -799,7 +799,7 @@ Before you download any pkgsrc files, yo current branch or the stable branch. The latter is forked on a quarterly basis from the current branch and only gets modified for security updates. The names of the stable branches are built from the year and the quarter, for example -2016Q4. +2017Q3. The second step is to decide how you want to download pkgsrc. You can get it as a tar file or via CVS. Both ways are described here. @@ -822,15 +822,12 @@ published at pkgsrc.tar.bz2 and pkgsrc.t You can fetch the same files using FTP. -The tar file for the stable branch 2016Q4 is in the directory pkgsrc-2016Q4 and +The tar file for the stable branch 2017Q3 is in the directory pkgsrc-2017Q3 and is also called pkgsrc.tar.gz. -To download a pkgsrc stable tarball, run: +To download the latest pkgsrc stable tarball, run: -$ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-20xxQy/pkgsrc.tar.gz - -Where pkgsrc-20xxQy is the stable branch to be downloaded, for example, " -pkgsrc-2016Q4". +$ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2017Q3/pkgsrc.tar.gz If you prefer, you can also fetch it using "wget", "curl", or your web browser. @@ -849,10 +846,7 @@ $ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/cu To fetch a specific pkgsrc stable branch, run: -$ cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r pkgsrc-20xxQy -P pkgsrc - -Where pkgsrc-20xxQy is the stable branch to be checked out, for example, " -pkgsrc-2016Q4" +$ cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r pkgsrc-2017Q3 -P pkgsrc This will create the directory pkgsrc/ in your /usr/ directory and all the package source will be stored under /usr/pkgsrc/. @@ -934,7 +928,7 @@ When updating pkgsrc, the CVS program ke But if you, for whatever reason, want to switch from the stable branch to the current one, you can do it by adding the option "-A" after the "update" keyword. To switch from the current branch back to the stable branch, add the " --rpkgsrc-2016Q4" option. +-rpkgsrc-2017Q3" option. 2.2.2.2. What happens to my changes when updating? --_----------=_1511783569190130--

2.1.2. Via anonymous CVS