From owner-freebsd-ports@FreeBSD.ORG Tue Jan 17 23:15:19 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F83316A41F for ; Tue, 17 Jan 2006 23:15:19 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id D854743D48 for ; Tue, 17 Jan 2006 23:15:18 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 22425 invoked by uid 399); 17 Jan 2006 23:15:17 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 17 Jan 2006 23:15:17 -0000 Message-ID: <43CD7A84.8040703@FreeBSD.org> Date: Tue, 17 Jan 2006 15:15:16 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <200601131703.37174.list-freebsd-2004@morbius.sent.com> <20060113204712.5403643c.jylefort@FreeBSD.org> <20060114095135.GA812@kyuzo.dunkelkammer.void> <43CA06D7.5010705@FreeBSD.org> <20060117101650.GA87895@chikuku.dunkelkammer.void> In-Reply-To: <20060117101650.GA87895@chikuku.dunkelkammer.void> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Distfiles and FTP Traffic-Shaping 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: Tue, 17 Jan 2006 23:15:19 -0000 Stefan Walter wrote: > Hi, > > Doug Barton, 15.01.06, 09:24h CET: > >>> MASTER_SORT_REGEX already exists. From my /etc/make.conf: >> Interesting. How would you teach this to avoid a certain site? > > I only looked briefly at /usr/ports/Mk/bsd.port.mk, but I don't think > that's possible. I had come to that same conclusion, I just hoped that I was wrong. :) > You could, of course, make sure that you list all other > SourceForge mirrors in your regex, or redefine MASTER_SITE_SOURCEFORGE > completely in /etc/make.conf (untested). Well that would likely work, the problem is that unless I keep on top of it, I would miss when new mirrors are added, or bad ones deleted. The solution I chose instead was to use RANDOMIZE_MASTER_SITES, which gives me 6/8 odds to get a site that isn't broken (there are two sites using IPv6 in that list that fetch doesn't play nicely with). Doug -- This .signature sanitized for your protection