From c7737260dbed70e663441b54307327b3078d8808 Mon Sep 17 00:00:00 2001 From: leot Date: Mon, 10 Sep 2018 12:12:34 +0000 Subject: doc/pkgsrc.*: regen --- doc/pkgsrc.html | 60 +++++++++++++++++++++++++++++++-------------------------- 1 file changed, 33 insertions(+), 27 deletions(-) (limited to 'doc/pkgsrc.html') diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index 20a53ac96cd..512429a883e 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -7109,25 +7109,31 @@ DEPENDS+= ImageMagick>=6.0:../../graphics/ImageMagick already have installed on his system, e.g. if your package installs the same set of files as another package in the pkgsrc tree or has the same PKGNAME.

-

These cases are handled automatically by the packaging tools - at package installation time and do not need to be handled - manually.

-

In case the conflicts can not be recognized automatically - (e.g., packages using the same config file location but no other - shared files), you can set CONFLICTS to a - space-separated list of packages (including version string) your - package conflicts with.

-

For example, if both foo/bar - and foo/baz - use the same config file, you would set in - foo/bar/Makefile:

+

For example, x11/libXaw3d + and x11/Xaw-Xpm + install the same shared library, thus you set in + pkgsrc/x11/libXaw3d/Makefile:

-CONFLICTS=      baz-[0-9]*
-
-

and in pkgsrc/foo/baz/Makefile:

+CONFLICTS= Xaw-Xpm-[0-9]* + +

and in pkgsrc/x11/Xaw-Xpm/Makefile:

-CONFLICTS=      bar-[0-9]*
-
+CONFLICTS= libXaw3d-[0-9]* + +

pkg_add(1) is able to detect attempts to install packages + that conflict with existing packages and abort. However, in many + situations this is too late in the process. Binary package managers + will not know about the conflict until they attempt to install the + package after already downloading it and all its dependencies. + Users may also waste time building a package and its dependencies + only to find out at the end that it conflicts with another package + they have installed.

+

To avoid these issues CONFLICTS entries + should be added in all cases where it is known that packages conflict + with each other. These CONFLICTS entries are + exported in pkg_summary(5) files and consumed by binary package + managers to inform users that packages cannot be installed onto + the target system.

@@ -8833,7 +8839,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? @@ -8878,7 +8884,7 @@ do? -

22.1.

+

22.1.

What is the difference between MAKEFLAGS, .MAKEFLAGS and @@ -8894,7 +8900,7 @@ do? -

22.2.

+

22.2.

What is the difference between MAKE, GMAKE and @@ -8912,7 +8918,7 @@ do? -

22.3.

+

22.3.

What is the difference between CC, PKG_CC and @@ -8930,7 +8936,7 @@ do? -

22.4.

+

22.4.

What is the difference between BUILDLINK_LDFLAGS, @@ -8943,7 +8949,7 @@ do? -

22.5.

+

22.5.

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

22.6.

+

22.6.

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

22.7.

+

22.7.

Which mailing lists are there for package developers?

@@ -9008,7 +9014,7 @@ do? -

22.8.

+

22.8.

Where is the pkgsrc documentation?

@@ -9056,7 +9062,7 @@ do? -

22.9.

+

22.9.

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

-- cgit v1.2.3