From cf86a8c1f938b0bd8a82db1fc659ff9bd65b0abb Mon Sep 17 00:00:00 2001
From: grant <grant@pkgsrc.org>
Date: Thu, 2 Jan 2003 06:18:48 +0000
Subject: add to PLIST issues: * LOWER_OPSYS. * platform specific PLIST
 handling.

---
 Packages.txt | 26 +++++++++++++++++++++-----
 1 file changed, 21 insertions(+), 5 deletions(-)

diff --git a/Packages.txt b/Packages.txt
index b38d8ab1761..524cb2f7929 100644
--- a/Packages.txt
+++ b/Packages.txt
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.275 2002/12/27 06:53:42 uebayasi Exp $
+# $NetBSD: Packages.txt,v 1.276 2003/01/02 06:18:48 grant Exp $
 ###########################################################################
 
 			==========================
@@ -895,11 +895,13 @@ to when dealing with the PLIST file (or files, see below!).
    the output of "uname -m", but that's no longer supported and has been
    removed.
 
- * ${OPSYS}, ${OS_VERSION}:
+ * ${OPSYS}, ${LOWER_OPSYS}, ${OS_VERSION}:
    Some packages want to embed the OS name and version into some paths.
-   to do this, use these two variables in PLIST. ${OPSYS} will be replaced
-   by output from "uname -s", ${OS_VERSION} will be set to what "uname -r"
-   gives.
+   To do this, use these variables in the PLIST:
+
+      * ${OPSYS} - output of "uname -s"
+      * ${LOWER_OPSYS} - lowercase common name (eg. "solaris")
+      * ${OS_VERSION} - "uname -r"
 
  * ${PKGLOCALEDIR}:
    Packages that install locale files should list them in the PLIST as
@@ -916,6 +918,20 @@ to when dealing with the PLIST file (or files, see below!).
    details. This modification of the PLIST file is done on a copy of it,
    not PLIST itself.
 
+ * Platform specific and differing PLISTs:
+   Some packages decide to install a different set of files based on
+   the operating system being used. These differences can be
+   automatically handled by using the following files:
+
+        * PLIST.common
+        * PLIST.${OPSYS}
+        * PLIST.common_end
+
+   If PLIST.${OPSYS} exists, these files are used instead of PLIST. This
+   allows packages which behave in this way to be handled gracefully.
+   Manually overriding PLIST_SRC for other more exotic uses is also
+   possible.
+
  * Semi-automatic PLIST generation:
    You can use the "make print-PLIST" command to output a PLIST that matches
    any new files since the package was extracted. See below for more 
-- 
cgit v1.2.3