Subject: bsd.pkg.mk and IPv6 issue
To: None <firstname.lastname@example.org>
From: Jun-ichiro itojun Hagino <email@example.com>
Date: 01/20/2000 17:02:19
I'm still wondering how IPv6-ready packages should be handled.
To summarize, there was rough consensus on nuke USE_INET6 (an explicit
flag to turn on IPv6 support) and go to HAVE_INET6 (an automatically
defined flag to turn on IPv6 support).
My goals are like this. For dual stack capable packages (like
- pre-1.4x users need to build packages. for them IPv6 support should
- for post-1.4x (after IPv6 merge), IPv6 support should always be
for packages which may break IPv4 part:
- prepare foo and foo6 separately (like apache/apache6)
- on pre-1.4x, foo6 will not be built (BROKEN)
- on post-1.4x, foo6 can be built fine
I'm still wondering how to identify the former case and the latter
case. Candidates are as follows:
- Check kernel AF_INET6 support - looks unwise. INET6 can be
- Check existence of certain file - like /usr/include/netinet6/ip6.h
I think the second option (certain file) is the way to go. If you have
any other ideas, please let me know.
other thing: is HAVE_INET6 the right name?