Re: pkg/36863 (mk/emulator/netbsd-compat.mk syntax problem on NetBSD 3 ?)

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR pkg/36863; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/36863 (mk/emulator/netbsd-compat.mk syntax problem on NetBSD 3 
?) 
Date: Fri, 31 Aug 2007 18:05:01 +0700

     Date:        Thu, 30 Aug 2007 16:59:40 +0000 (UTC)
     From:        jlam%NetBSD.org@localhost
     Message-ID:  <20070830165940.2C78663B8B5%narn.NetBSD.org@localhost>
 
   | Actually, it looks like the commit that uses COMPAT_PKG instead of DISTNAME
   | is understood by lintpkgsrc, although not by pkglint.  Could you test
   | whether the problem still exists on your machine?
 
 No, gone now.   I had not considered that lintpkgsrc might have its own 
 Makefile parser (though I do now kind of recall something about it, and
 it does make some kind of sense) so I hadn't really considered that it
 might be an issue.   While I had an up to date pkgsrc when I tested this,
 I hadn't upgraded pkglint to its most recent version (my general upgrade
 procedure relies upon lintpkgsrc working to tell me what I am supposed
 to upgrade - when it gives errors I tend to simply put off upgrading
 everything until it is quiet again - and recently there have been a
 whole bunch of changes that have caused errors from lintpkgsrc).
 
 I upgraded pkglint, and the problem vanished.   Your commits might, or
 might not, have been included when I did the test (I have them now, but
 I actually tested it a while ago, and my repository was still in the process
 of one of its twice daily updates - I suspect I missed the commits in the
 early morning (my timezone) update.
 
   | A command-line for the lintpkgsrc command you executed that
   | generated those errors wasn't provided
 
 I didn't really think it was relevant, as almost any execution is going
 to be processing the pkg makefile(s), and it was the makefile parsing that
 was failing, so how lintpkgsrc planned on using the result of all of that
 shouldn't really have been relevant.
 
 But for completeness, it was
 
        pkg_comp chroot lintpkgsrc -p
 
 (with the output then piped into grep, to get rid of all the messages
 about out of date packages (symlinks) in the various packages/category
 directory, and retain only the stuff in packages/All - but that cannot
 possibly be relevant).
 
 The pkgcomp_chroot is needed to set up the 3.0 environment (without that
 it would be using some random out of date version of -current).
 
 This PR can get closed.   Thanks.
 
 kre