I've just implemented Itojun's suggestion, and from now only packages that
contain USE_INET6 in their BUILD_DEFS (regular expression:
"^BUILD_DEFS.*=.*USE_INET6") will be listed in the README-IPv6.html on the
FTP server. So everyone doing v6-enabled packages please don't forget
to add USE_INET6 to BUILD_DEFS. Thanks!


 - Hubert

-- 
Microsoft: "Where do you want to go today?"
Linux:     "Where do you want to be tomorrow?"
BSD:       "Are you guys coming, or what?"

---------- Forwarded message ----------
Date: Thu, 30 Mar 2000 07:43:07 +0900
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
To: hubert.feyrer@informatik.fh-regensburg.de
Cc: tech-pkg@netbsd.org
Subject: Re: IPv6 package detection 


>> 	Hello, how does
>> 	ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/README-IPv6.html
>> 	detect IPv6-ready pkgsrc?  I wonder why net/bind9 is considered as
>> 	IPv6-ready package, while it has no BUILD_DEFS+=USE_INET6. 
>>From pkgsrc/Makefile:
>README-IPv6.html:
>        @grep -l USE_INET6 */*/Makefile | sed s,.Makefile,, >$@.pkgs
>	...
>If we find something smarter, we sure can use it, but I didn't find
>anything better.

	Thank you for clarfication.
	Hmm... so, by having the following comment in Makefile it will be
	considered IPv6 ready :-)

# We do not support IPv6, do not define USE_INET6 yet

>> What is
>> 	the right way to write Makefile for:
>> 	- pkgsrc that are not IPv6 ready
>> 	- pkgsrc that are always IPv6 ready
>> 	- pkgsrc that autodetects IPv6 readiness
>AFAIK we don't have any way to express this right now.

	I think mandating BUILD_DEFS+=USE_INET6 on IPv6 ready (both always
	and autodetect), and checking for /^BUILD_DEFS.?=.*USE_INET6/
	would be more stable.

itojun