From 9c92d0adc617cd312a8f48dd0a99aa2077589d20 Mon Sep 17 00:00:00 2001 From: wiz Date: Tue, 16 Apr 2013 13:56:04 +0000 Subject: regen --- doc/pkgsrc.html | 80 ++++++++++++++++++++++++++++++++++++++++----------------- doc/pkgsrc.txt | 32 ++++++++++++++++++----- 2 files changed, 83 insertions(+), 29 deletions(-) (limited to 'doc') diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index 930c9d5f1a9..56805bfdc71 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -5667,6 +5667,29 @@ BUILDLINK_TREE+= -tiff buildlink3.mk file is included. Dependencies are only added for directly include buildlink3.mk files.

+

When providing a buildlink3.mk and + including other buildlink3.mk files in it, + please only add necessary ones. I.e. those whose libraries or + header files are automatically exposed when the package is + use.

+

In particular, if only an executable + (bin/foo) is linked against a library, that + library does not need to be propagated in the + buildlink3.mk file.

+

The following steps should help you decide if a + buildlink3.mk file needs to be included: +

+
+

+

@@ -7615,7 +7638,7 @@ TOOLS_PLATFORM.true?= true # shell builtin

18.4. Questions regarding the tools

-
+
18.4.1. How do I add a new tool?
18.4.2. How do I get a list of all available @@ -7634,7 +7657,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

18.4.1.

+

18.4.1.

How do I add a new tool?

@@ -7644,7 +7667,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

18.4.2.

+

18.4.2.

How do I get a list of all available tools?

@@ -7655,7 +7678,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 @@ -8983,17 +9006,28 @@ REPLACE_FILES.tcl= # list of tcl scripts which need to be fixed, the installed .packlist file generated by most perl5 modules. This is invoked by defining PERL5_PACKLIST to a space-separated list of - paths to packlist files, e.g.:

+ packlist files relative to PERL5_PACKLIST_DIR + (PERL5_INSTALLVENDORARCH by default), + e.g.:

-PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist
+PERL5_PACKLIST= auto/Pg/.packlist
-

The variables PERL5_SITELIB, - PERL5_SITEARCH, and - PERL5_ARCHLIB represent the three locations - in which perl5 modules may be installed, and may be used by - perl5 packages that don't have a packlist. These three - variables are also substituted for in the - PLIST.

+

The perl5 config variables + installarchlib, + installscript, + installvendorbin, + installvendorscript, + installvendorarch, + installvendorlib, + installvendorman1dir, and + installvendorman3dir represent those + locations in which components of perl5 modules may be installed, + provided as variable with uppercase and prefixed with + PERL5_, e.g. PERL5_INSTALLARCHLIB + and may be used by perl5 packages that don't have a packlist. + These variables are also substituted for in the + PLIST as uppercase prefixed with + PERL5_SUB_.

@@ -9676,7 +9710,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? @@ -9721,7 +9755,7 @@ do? -

22.1.

+

22.1.

What is the difference between MAKEFLAGS, .MAKEFLAGS and @@ -9737,7 +9771,7 @@ do? -

22.2.

+

22.2.

What is the difference between MAKE, GMAKE and @@ -9755,7 +9789,7 @@ do? -

22.3.

+

22.3.

What is the difference between CC, PKG_CC and @@ -9773,7 +9807,7 @@ do? -

22.4.

+

22.4.

What is the difference between BUILDLINK_LDFLAGS, @@ -9786,7 +9820,7 @@ do? -

22.5.

+

22.5.

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

22.6.

+

22.6.

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

22.7.

+

22.7.

Which mailing lists are there for package developers?

@@ -9851,7 +9885,7 @@ do? -

22.8.

+

22.8.

Where is the pkgsrc documentation?

@@ -9899,7 +9933,7 @@ do? -

22.9.

+

22.9.

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

diff --git a/doc/pkgsrc.txt b/doc/pkgsrc.txt index b947fabdf03..d7a28c9fdee 100644 --- a/doc/pkgsrc.txt +++ b/doc/pkgsrc.txt @@ -4824,6 +4824,22 @@ headers and libraries for these dependencies are also symlinked into $ {BUILDLINK_DIR} whenever the pkg buildlink3.mk file is included. Dependencies are only added for directly include buildlink3.mk files. +When providing a buildlink3.mk and including other buildlink3.mk files in it, +please only add necessary ones. I.e. those whose libraries or header files are +automatically exposed when the package is use. + +In particular, if only an executable (bin/foo) is linked against a library, +that library does not need to be propagated in the buildlink3.mk file. + +The following steps should help you decide if a buildlink3.mk file needs to be +included: + + * Run ldd on all installed libraries and look against what other libraries + they link. The packages providing these must be buildlinked. + + * Look at the installed header files: What headers do they include? The + packages providing these files must be buildlinked. + 14.2.2. Updating BUILDLINK_API_DEPENDS.pkg and BUILDLINK_ABI_DEPENDS.pkg in buildlink3.mk files @@ -7496,15 +7512,19 @@ Perl5 modules will install into different places depending on the version of perl used during the build process. To address this, pkgsrc will append lines to the PLIST corresponding to the files listed in the installed .packlist file generated by most perl5 modules. This is invoked by defining PERL5_PACKLIST to -a space-separated list of paths to packlist files, e.g.: +a space-separated list of packlist files relative to PERL5_PACKLIST_DIR +(PERL5_INSTALLVENDORARCH by default), e.g.: -PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist +PERL5_PACKLIST= auto/Pg/.packlist -The variables PERL5_SITELIB, PERL5_SITEARCH, and PERL5_ARCHLIB represent the -three locations in which perl5 modules may be installed, and may be used by -perl5 packages that don't have a packlist. These three variables are also -substituted for in the PLIST. +The perl5 config variables installarchlib, installscript, installvendorbin, +installvendorscript, installvendorarch, installvendorlib, installvendorman1dir, +and installvendorman3dir represent those locations in which components of perl5 +modules may be installed, provided as variable with uppercase and prefixed with +PERL5_, e.g. PERL5_INSTALLARCHLIB and may be used by perl5 packages that don't +have a packlist. These variables are also substituted for in the PLIST as +uppercase prefixed with PERL5_SUB_. 19.6.7. Packages installing info files -- cgit v1.2.3