>> gnome-python package uses an invalid registration name, which causes
>> lintpkgsrc not to recognize the package:
>> 
>> Unknown package: 'py22-gnome' version 1.4.0nb3
>> 
>>>How-To-Repeat:
>> Instal gnome-python and run 'lintpkgsrc -i'.
>>>Fix:
>> Stop using version dependent naming and use 'gnome-python' instead.
>
>Wouldn't that break many binary packages? Why do you suppose it was
>done in the first place?

i noticed this sort of problem a day or so ago.

synopsis:

	# lintpkgsrc -D pkgsrc/x11/gnome-python 2>/dev/null | grep PKGNAME
        PKGNAME = UNDEFINED-gnome-1.4.0
	# grep PKGNAME pkgsrc/x11/gnome-python/Makefile 
	PKGNAME=                ${PYPKGPREFIX}-gnome-1.4.0
	# lintpkgsrc -D pkgsrc/x11/gnome-python 2>/dev/null | grep PYPKGPREFIX
	# 

solution:

	teach lintpkgsrc how to parse more of pkgsrc/lang/python/*.mk,
	or maybe how to do the kind of lazy variable evaluation that
	make does (maybe it already does this...i dunno).
	
	afiact, they seem to use constructs that lintpkgsrc doesn't
	grok entirely.

aside:

	try "lintpkgsrc -E file" and grep for UNDEF in file

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."