From owner-freebsd-ports@FreeBSD.ORG Mon Jan 8 00:57:31 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F23016A407 for ; Mon, 8 Jan 2007 00:57:31 +0000 (UTC) (envelope-from cristi@net.utcluj.ro) Received: from bavaria.utcluj.ro (bavaria.utcluj.ro [193.226.5.35]) by mx1.freebsd.org (Postfix) with ESMTP id BA35213C441 for ; Mon, 8 Jan 2007 00:57:30 +0000 (UTC) (envelope-from cristi@net.utcluj.ro) Received: from localhost (localhost [127.0.0.1]) by bavaria.utcluj.ro (Postfix) with ESMTP id 8BAF77F285 for ; Mon, 8 Jan 2007 02:28:57 +0200 (EET) X-Virus-Scanned: by the daemon playing with your mail on bavaria.utcluj.ro Received: from bavaria.utcluj.ro ([127.0.0.1]) by localhost (bavaria.utcluj.ro [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e60kLki9pGSC for ; Mon, 8 Jan 2007 02:28:56 +0200 (EET) Received: from [172.27.2.200] (c7.campus.utcluj.ro [193.226.6.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bavaria.utcluj.ro (Postfix) with ESMTP id 3C9337F282 for ; Mon, 8 Jan 2007 02:28:56 +0200 (EET) Message-ID: <45A19046.7060506@net.utcluj.ro> Date: Mon, 08 Jan 2007 02:28:54 +0200 From: Cristian KLEIN Organization: Data Communication Center - Technical University of Cluj-Napoca User-Agent: Icedove 1.5.0.7 (X11/20061013) MIME-Version: 1.0 To: ports@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Regarding dns/djbdns X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 00:57:31 -0000 Hello, I have contacted this e-mail address as this is what "make maintainer" gave me for "dns/djbdns". I just wanted to tell you that the IPv6 patch destroys the location facility (or views, in BIND terms) of tinydns. Considering the fact that IPv6 and locations are rarely used, I think that the best solution would be to simply warn the user. It wouldn't hurt to also inform upstream. Should you require further details or if I might be of any help, please don't hesitate to contact me. Thanks.