Date: 07 Jan 2000 17:57:58 -0800 From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) To: sumikawa@ebina.hitachi.co.jp Cc: freebsd-ports@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: IPv6-enable ports Message-ID: <vqc7lhlfhp5.fsf@silvia.hip.berkeley.edu> In-Reply-To: sumikawa@ebina.hitachi.co.jp's message of "Sat, 8 Jan 2000 00:02:51 %2B0900 (JST)" References: <200001061955.EAA34652@prince.net.ebina.hitachi.co.jp> <vqc3dsakp95.fsf@silvia.hip.berkeley.edu> <200001071502.AAA46153@prince.net.ebina.hitachi.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: sumikawa@ebina.hitachi.co.jp
* Almost of applications work fine, but downwards compatibility is
* depends on each implementations in general.
For those that work for both v4 and v6, I think you should just go
ahead and enable IPv6 by default. (I'm assuming the patches are not
*that* big.) I don't want your jobs to be any harder than it already
is.
For those that only work for one, I suggest you make v4 the default
and add a "slave" port that sets the v6 option on. Something like
this:
ports/ftp/wu-ftpd: normal port, with USE_INET6 check you suggested
ports/ftp/wu-ftpd+ipv6: slave port with only the Makefile
===
USE_INET6= yes
MASTERDIR= ${.CURDIR}/../wu-ftpd
.include "${MASTERDIR}/Makefile"
===
That way we can easily build packages for both v4 and v6 users.
-PW
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqc7lhlfhp5.fsf>