From 79bcfccbad3a92f6333d42f728e445808f2d99db Mon Sep 17 00:00:00 2001 From: snj Date: Fri, 3 Apr 2009 01:56:39 +0000 Subject: regen --- doc/pkgsrc.html | 86 +++++++++++++++++++++++---------------------------------- 1 file changed, 34 insertions(+), 52 deletions(-) (limited to 'doc/pkgsrc.html') diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index 1ee25bf722a..bd607c1604f 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -2434,7 +2434,7 @@ PKG_DEFAULT_OPTIONS= -arts -dvdread -esound PKG_OPTIONS.kdebase= debug -sasl PKG_OPTIONS.apache= suexec

It is important to note that options that were specifically - suggested by the package maintainer must be explicitely removed if + suggested by the package maintainer must be explicitly removed if you do not wish to include the option. If you are unsure you can view the current state with make show-options.

The following settings are consulted in the order given, and @@ -5307,12 +5307,12 @@ PLIST_SUBST+= SOMEVAR="somevalue"

This replaces all occurrences of “${SOMEVAR}” in the PLIST with “somevalue”.

-

The PLIST_VARS can be used to simplify +

The PLIST_VARS variable can be used to simplify the common case of conditionally including some PLIST entries. It can be done by adding PLIST_VARS+=foo and - setting the coresponding PLIST.foo variable - to yes, if the entry should be included. + setting the corresponding PLIST.foo variable + to yes if the entry should be included. This will substitute “${PLIST.foo}” in the PLIST with either “""” or @@ -5573,47 +5573,28 @@ BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0 buildlink3.mk is taken from pkgsrc/graphics/tiff:

-# $NetBSD: buildlink3.mk,v 1.7 2004/03/18 09:12:12 jlam Exp $
+# $NetBSD: buildlink3.mk,v 1.16 2009/03/20 19:24:45 joerg Exp $
 
-BUILDLINK_DEPTH:=       ${BUILDLINK_DEPTH}+
-TIFF_BUILDLINK3_MK:=    ${TIFF_BUILDLINK3_MK}+
+BUILDLINK_TREE+=	tiff
 
-.if ${BUILDLINK_DEPTH} == "+"
-BUILDLINK_DEPENDS+=     tiff
-.endif
-
-BUILDLINK_PACKAGES:=    ${BUILDLINK_PACKAGES:Ntiff}
-BUILDLINK_PACKAGES+=    tiff
+.if !defined(TIFF_BUILDLINK3_MK)
+TIFF_BUILDLINK3_MK:=
 
-.if ${TIFF_BUILDLINK3_MK} == "+"
-BUILDLINK_API_DEPENDS.tiff+=        tiff>=3.6.1
-BUILDLINK_PKGSRCDIR.tiff?=      ../../graphics/tiff
-.endif  # TIFF_BUILDLINK3_MK
+BUILDLINK_API_DEPENDS.tiff+=	tiff>=3.6.1
+BUILDLINK_ABI_DEPENDS.tiff+=	tiff>=3.7.2nb1
+BUILDLINK_PKGSRCDIR.tiff?=	../../graphics/tiff
 
 .include "../../devel/zlib/buildlink3.mk"
 .include "../../graphics/jpeg/buildlink3.mk"
+.endif # TIFF_BUILDLINK3_MK
 
-BUILDLINK_DEPTH:=       ${BUILDLINK_DEPTH:S/+$//}
+BUILDLINK_TREE+=	-tiff

The header and footer manipulate - BUILDLINK_DEPTH, which is common across all + BUILDLINK_TREE, which is common across all buildlink3.mk files and is used to track - at what depth we are including - buildlink3.mk files.

-

The first section controls if the dependency on - pkg is added. - BUILDLINK_DEPENDS is the global list of - packages for which dependencies are added by - buildlink3.

-

The second section advises pkgsrc that the - buildlink3.mk file for - pkg has been included at some point. - BUILDLINK_PACKAGES is the global list of - packages for which buildlink3.mk files - have been included. It must always be - appended to within a buildlink3.mk - file.

-

The third section is protected from multiple inclusion + the dependency tree.

+

The main section is protected from multiple inclusion and controls how the dependency on pkg is added. Several important variables are set in the section:

-

The last section includes any +

This section can additionally include any buildlink3.mk needed for pkg's library dependencies. Including these buildlink3.mk files @@ -5701,7 +5682,8 @@ BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//} ${BUILDLINK_DIR} whenever the pkg buildlink3.mk - file is included.

+ file is included. Dependencies are only added for directly + include buildlink3.mk files.

@@ -6570,7 +6552,7 @@ details.

built. Building a package is separated into different phases (for example fetch, build, install), all of which are - described in the following sections. Each phase is splitted into + described in the following sections. Each phase is split into so-called stages, which take the name of the containing phase, prefixed by one of pre-, do- or post-. (Examples are @@ -7661,7 +7643,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

18.4.1.

+

18.4.1.

How do I add a new tool?

@@ -7671,7 +7653,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

18.4.2.

+

18.4.2.

How do I get a list of all available tools?

@@ -7682,7 +7664,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 @@ -9694,7 +9676,7 @@ do? -

22.1.

+

22.1.

What is the difference between MAKEFLAGS, .MAKEFLAGS and @@ -9710,7 +9692,7 @@ do? -

22.2.

+

22.2.

What is the difference between MAKE, GMAKE and @@ -9728,7 +9710,7 @@ do? -

22.3.

+

22.3.

What is the difference between CC, PKG_CC and @@ -9746,7 +9728,7 @@ do? -

22.4.

+

22.4.

What is the difference between BUILDLINK_LDFLAGS, @@ -9759,7 +9741,7 @@ do? -

22.5.

+

22.5.

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

22.6.

+

22.6.

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

22.7.

+

22.7.

Which mailing lists are there for package developers?

@@ -9824,7 +9806,7 @@ do? -

22.8.

+

22.8.

Where is the pkgsrc documentation?

@@ -9872,7 +9854,7 @@ do? -

22.9.

+

22.9.

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

@@ -10119,7 +10101,7 @@ followed:

  • Get a list of all the tarballs that form the new release by using the following commands. These will leave the full list of the - components's distfiles into the list.txt + components' distfiles into the list.txt file:

    % echo ls "*.tar.bz2" | \
     ftp -V ftp://ftp.gnome.org/pub/gnome/platform/x.y/x.y.z/sources/ | \
@@ -10911,7 +10893,7 @@ Connected to ftp.plig.net.
 230-Please note that all transfers from this FTP site are logged. If you
 230-do not like this, please disconnect now.
 230-
-230-This arhive is available via
+230-This archive is available via
 230-
 230-HTTP:  http://ftp.plig.org/
 230-FTP:   ftp://ftp.plig.org/     (max 500 connections)
-- 
cgit v1.2.3