On Wed, 7 Jul 1999 itojun@iijlab.net wrote:
> 	The issues that how to manage a IPv6-ready pkgsrc which changes
> 	things too much from IPv4-only pkgsrc.  For example, apache136 with
> 	IPv6 support needs to change apache module API (to avoid struct
> 	in_addr), so it is not compatible with some 3rd-party apache module.
> 	I can't just change normal apache13 directory.
> 	Also, generating files/md5 becomes a bit tricker.
<long list deleted>

Hum... i'd say include in the existing packages as much as possibel (and
makes sense). Beyond that we could do several things:
1. create a pkgsrc/inet6 or pkgsrc/ipv6 and put all the packags   
   there. 
2. place the packages besides their v4 cousins, and name them different:
	pkgsrc/foo/bar
	pkgsrc/foo/bar-ipv6

I'd prefer #2, and with the recent additions to bsd.pkg.mk, this shouldn't
be a problem. Maybe other people have other ideas, though? :)


 - Hubert

-- 
NetBSD - Better for your uptime than Viagra