Subject: pkg/24006: PKGNAME is not clearly explained in packages(7) or /usr/pkgsrc/Packages.txt
To: None <>
From: None <>
List: netbsd-bugs
Date: 01/06/2004 14:30:08
>Number:         24006
>Category:       pkg
>Synopsis:       PKGNAME is not clearly explained in packages(7) or /usr/pkgsrc/Packages.txt
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 06 19:31:00 UTC 2004
>Originator:     Joachim Thiemann
>Release:        NetBSD 1.6ZG
Joachim Thiemann                   
Speech and Audio Coding Research Group
        Department of Electrical & Computer Engineering (GEGI)
University of Sherbrooke     Sherbrooke (Quebec)     J1K 2R1      CANADA
System: NetBSD codaget3002 1.6ZG NetBSD 1.6ZG (IBMT30) #1: Thu Dec 18 15:21:32 EST 2003 thiemann@codaget3002:/home/build-i386/sys/arch/i386/compile/IBMT30 i386
Architecture: i386
Machine: i386
	The purpose of the PKGNAME variable of package Makefiles is not clearly
	explained in packages(7), nor is there anything but a brief mention in 
	section 4.1 of Packages.txt, yet it can lead to a fatal report from pkglint.
	man 7 packages
	- or -
        more /usr/pkgsrc/Packages.txt
	I am suggesting an expansion of the current paragraph, such as

	PKGNAME	Name of the package file if the package file to create if the
		default (derived from ${DISTNAME}) is not really proper for
		the packages sytem.  This may be the case if e.g. the version
		number of the tarball is not in a format that the packages
		system understands.

	The Packages.txt could have a specific exaple in its eplanation of the
	Makefile, which could be added in the "gotchas" of section 4.1:

 - Set PKGNAME if pkglint complains about it in some way.  This may be caused
   by a versioning scheme that is not understood by the packages tools.  For
   exaple, if DISTNAME=foo-v7r2, set PKGNAME=foo-7.2  (see also under the -e
   option of pkg_info(1))