Subject: Re: pkg/20025: gnome-python package's registration is invalid
To: Frederick Bruckman <firstname.lastname@example.org>
From: Andrew Brown <email@example.com>
Date: 01/26/2003 23:29:48
>> gnome-python package uses an invalid registration name, which causes
>> lintpkgsrc not to recognize the package:
>> Unknown package: 'py22-gnome' version 1.4.0nb3
>> Instal gnome-python and run 'lintpkgsrc -i'.
>> 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.
# lintpkgsrc -D pkgsrc/x11/gnome-python 2>/dev/null | grep PKGNAME
PKGNAME = UNDEFINED-gnome-1.4.0
# grep PKGNAME pkgsrc/x11/gnome-python/Makefile
# lintpkgsrc -D pkgsrc/x11/gnome-python 2>/dev/null | grep PYPKGPREFIX
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
try "lintpkgsrc -E file" and grep for UNDEF in file
|-----< "CODE WARRIOR" >-----|
firstname.lastname@example.org * "ah! i see you have the internet
email@example.com (Andrew Brown) that goes *ping*!"
firstname.lastname@example.org * "information is power -- share the wealth."