summaryrefslogtreecommitdiff
path: root/Packages.txt
diff options
context:
space:
mode:
authorhubertf <hubertf>2000-07-06 15:08:30 +0000
committerhubertf <hubertf>2000-07-06 15:08:30 +0000
commit66eb474d0e25f4da3bedaf811875d2c343804842 (patch)
treeb871d15aa7f0269e6fdd0daad298e21d166570dc /Packages.txt
parent68f4a0b908ca239461c8f54dc090f92e4b3cd929 (diff)
downloadpkgsrc-66eb474d0e25f4da3bedaf811875d2c343804842.tar.gz
Add some bits for PKG_DEVELOPER
Diffstat (limited to 'Packages.txt')
-rw-r--r--Packages.txt24
1 files changed, 19 insertions, 5 deletions
diff --git a/Packages.txt b/Packages.txt
index d67d1247498..97ad9542ab6 100644
--- a/Packages.txt
+++ b/Packages.txt
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.93 2000/07/01 20:12:03 hubertf Exp $
+# $NetBSD: Packages.txt,v 1.94 2000/07/06 15:08:30 hubertf Exp $
###########################################################################
==========================
@@ -401,10 +401,12 @@ will compile and run perfectly on NetBSD. The files are applied
successively in alphabetic order (as returned by a shell "patches/patch-*"
glob expansion), so patch-aa is applied before patch-ab etc.
-The patch-?? files should be in diff -bu format, and apply without a fuzz
-to avoid problems. Furthermore, do not put changes for more than one file
-into a single patch-file, as this will make future modifications more
-difficult.
+The patch-?? files should be in diff -bu format, and apply without
+a fuzz to avoid problems. (The latter condition is ensured by
+setting PKG_DEVELOPER in /etc/mk.conf - the build will fail if a
+patch applies with fuzz only). Furthermore, do not put changes
+for more than one file into a single patch-file, as this will make
+future modifications more difficult.
One important thing to mention is to pay attention that no RCS IDs get
stored in the patch files, as these will cause problems when later checked
@@ -965,6 +967,12 @@ The main targets used during the build process defined in bsd.pkg.mk are:
applied, files ending in .orig or .rej are ignored. Any special
options to patch(1) can be handed in PATCH_DIST_ARGS. See section
4.3 for more details.
+
+ If PKG_DEVELOPER is set in /etc/mk.conf, patch is given special args
+ to make it fail if the patches with some lines of fuzz. Please fix
+ (regen) the patches so that they apply cleanly. The rationale behind
+ this is that patches that apply cleanly may end up being applied in the
+ wrong place, and cause severe harm there.
* configure:
Most pieces of software need information on the header files,
@@ -1164,6 +1172,11 @@ perform the equivalent of:
host, and can be invoked from the top-level pkgsrc Makefile by using the
target "show-host-specific-pkgs"
+ * check-shlibs:
+ After a package is installed, check all it's binaries and (on ELF
+ platforms) shared libraries if they find the shared libs they need.
+ Run by default if PKG_DEVELOPER is set in /etc/mk.conf.
+
8 Debugging
===========
@@ -1174,6 +1187,7 @@ order to get a package working. Please note this is basically the
same as what was explained in the previous sections, only with some
debugging aids.
+ - Make sure PKG_DEVELOPER=1 is in /etc/mk.conf
- Retrieve port from FreeBSD collection
- Fix RCS-ID in the package's Makefile, see section 4.1.
- Import unchanged FreeBSD source (ONLY if you have cvs access, not needed