Subject: Re: RESTRICTED binary packages on ftp.netbsd.org
To: None <firstname.lastname@example.org>
From: David Brownlee <email@example.com>
Date: 01/03/2000 15:17:03
On Thu, 30 Dec 1999, Christoph Badura wrote:
> Testing for RESTRICTED in the Makefile isn't enough. bsd.pkg.mk sets
> RESTRICTED automatically when KERBEROS is enabled. And only the
> kerberised pkg is restricted. Hmm... Looks like LICENCE and KERBEROS
> is supposed to be recorded in the BUILD_INFO for the binary pkg (The
> LICENCE for my ssh pkg isn't useful, though). You could check for that
> in the actual binary pkg.
> Maybe we should put RESTRICTED into the BUILD_INFO too and be done with
Most definitely - then we can ignore the pkgsrc src altogether
when checking for RESTRICTED and just validate the binary
packages. Is this on anyones TODO?
> > qpopper-2.53
> At least this one is likely to be a false positive. It becomes restricted
> only if it is compiled with Kerberos support enabled. I assume Kimmo missed
> that one when he rototilled the Kerberos stuff.
I've tweaked lintpkgsrc to parse .if statements a touch better
(it now qualifies as 'badly' :), so it no longer gets this