>Number:         19891
>Category:       pkg
>Synopsis:       pkg_chk can't handle python packages
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jan 17 07:59:01 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Robert Elz
>Release:        NetBSD 1.6K   ---   pkgsrc 2003-01-15
>Organization:
	Prince of Songkla University
>Environment:
System: NetBSD delta.cs.mu.OZ.AU 1.6K NetBSD 1.6K (DELTA) #6: Sat Dec 21 23:51:46 EST 2002 kre@delta.cs.mu.OZ.AU:/usr/src/sys/arch/i386/compile/DELTA i386
Architecture: i386
Machine: i386
>Description:
	pkg_ckh (pgk_chk -i in particular) can't find the pkgsrc
	directory for those python packages that build the version
	string into their package name (but which doesn't exist in
	the pkgsrc name anywhere)
>How-To-Repeat:
	install pkgtools/pkg_chk
	install pkgtools/py-Tk   (doesn't matter which python version)
	run pkg_chk -i

	observe the strange output for py22-Tk (or py21-Tk or whatever)
>Fix:
	BTHOOM.
	I assume that pkg_chk uses the PKGPATH from +BUILD_INFO
	so it ought to be able to locate the correct pkgsrc directory.
	Then, at least assuming python versions haven't altered
	(which I don't think I managed to achieve - the relevant system
	and I aren't in the same location right now) it should be
	possible to have make print the current package version (which
	would include the python version) - which should be enough to
	detect the correct state of affairs.
>Release-Note:
>Audit-Trail:
>Unformatted: