From 4154195836c73be50863dd2b2227ea7649251571 Mon Sep 17 00:00:00 2001 From: weinem Date: Tue, 19 Feb 2008 01:06:31 +0000 Subject: regen --- doc/pkgsrc.html | 53 ++++++++++++++++++++++++++--------------------------- 1 file changed, 26 insertions(+), 27 deletions(-) (limited to 'doc/pkgsrc.html') diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index 0756904f938..7b6dc9d1860 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -970,8 +970,8 @@ release=pkgsrc in it, see the examples in /usr/share/examples/supfiles, and that the /usr/pkgsrc directory exists. Then, simply - run sup -v - /path/to/your/supfile.

+ run:

+
$ sup -v /path/to/your/supfile.

@@ -979,18 +979,16 @@ release=pkgsrc

To do an initial (full) checkout of pkgsrc, you first have to set some environment variables. For the C-Shell, type:

-
-    % setenv CVSROOT anoncvs@anoncvs.NetBSD.org:/cvsroot
-    % setenv CVS_RSH ssh
+
% setenv CVSROOT anoncvs@anoncvs.NetBSD.org:/cvsroot
+% setenv CVS_RSH ssh
 

 
Or, the same for the bourne shell:

-
-    $ export CVSROOT="anoncvs@anoncvs.NetBSD.org:/cvsroot"
-    $ export CVS_RSH="ssh"
+
$ export CVSROOT="anoncvs@anoncvs.NetBSD.org:/cvsroot"
+$ export CVS_RSH="ssh"
 

-
By default, cvs doesn't do things like most people would
+
By default, CVS doesn't do things like most people would
 	expect it to do. But there is a
-	way to convince cvs, by creating a file called
+	way to convince CVS, by creating a file called
 	.cvsrc in your home directory and saving
 	the following lines to it. This file will save you lots of
 	headache and some bug reports, so we strongly recommend it. You
@@ -1007,7 +1005,7 @@ rdiff -u
 

 
To fetch a specific pkgsrc stable branch from scratch, run:

 
$ cd /usr
-	$ cvs checkout -r pkgsrc-200xQy -P pkgsrc

+$ cvs checkout -r pkgsrc-200xQy -P pkgsrc

Where pkgsrc-200xQy is the stable branch to be checked out, for example, “pkgsrc-2007Q4”

This will create the directory pkgsrc/ @@ -1015,7 +1013,7 @@ rdiff -u will be stored under /usr/pkgsrc/.

To fetch the pkgsrc current branch, run:

$ cd /usr
-$ cvs checkout -r -P pkgsrc
+$ cvs checkout -P pkgsrc

@@ -1054,8 +1052,9 @@ rdiff -u 2.2.2. Via CVS

To update pkgsrc via CVS, make sure the environment variable CVS_RSH is set as above. Then, - change to the pkgsrc directory and run:

-
$ cvs update -dP
+ change to the pkgsrc directory and run cvs:

+
$ cd /usr/pkgsrc
+$ cvs update -dP

2.2.2.1. Switching between different pkgsrc branches

@@ -1065,7 +1064,7 @@ rdiff -u by adding the option “-A” after the “update” keyword. To switch from the current branch back to the stable branch, add the - “-rpkgsrc-2007Q1” option.

+ “-rpkgsrc-2007Q4” option.

@@ -7474,7 +7473,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

18.4.1.

+

18.4.1.

How do I add a new tool?

@@ -7484,7 +7483,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

18.4.2.

+

18.4.2.

How do I get a list of all available tools?

@@ -7495,7 +7494,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

18.4.3.

+

18.4.3.

How can I get a list of all the tools that a package is using while being built? I want to know whether it @@ -9497,7 +9496,7 @@ do? -

22.1.

+

22.1.

What is the difference between MAKEFLAGS, .MAKEFLAGS and @@ -9513,7 +9512,7 @@ do? -

22.2.

+

22.2.

What is the difference between MAKE, GMAKE and @@ -9531,7 +9530,7 @@ do? -

22.3.

+

22.3.

What is the difference between CC, PKG_CC and @@ -9549,7 +9548,7 @@ do? -

22.4.

+

22.4.

What is the difference between BUILDLINK_LDFLAGS, @@ -9562,7 +9561,7 @@ do? -

22.5.

+

22.5.

Why does make show-var VARNAME=BUILDLINK_PREFIX.foo @@ -9578,7 +9577,7 @@ do? -

22.6.

+

22.6.

What does ${MASTER_SITE_SOURCEFORGE:=package/} mean? I @@ -9602,7 +9601,7 @@ do? -

22.7.

+

22.7.

Which mailing lists are there for package developers?

@@ -9627,7 +9626,7 @@ do? -

22.8.

+

22.8.

Where is the pkgsrc documentation?

@@ -9675,7 +9674,7 @@ do? -

22.9.

+

22.9.

I have a little time to kill. What shall I do?

-- cgit v1.2.3