Date: Thu, 22 Jul 2010 20:06:35 +0200 From: Emanuel Haupt <ehaupt@FreeBSD.org> To: RW <rwmaillists@googlemail.com> Cc: ports@FreeBSD.org Subject: Re: MASTER_SITE defined by google search result Message-ID: <20100722200635.7f54c356.ehaupt@FreeBSD.org> In-Reply-To: <20100722183537.5382b6d5@gumby.homeunix.com> References: <20100722121731.34b47a2a.ehaupt@FreeBSD.org> <20100722183537.5382b6d5@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
RW <rwmaillists@googlemail.com> wrote: > On Thu, 22 Jul 2010 12:17:31 +0200 > Emanuel Haupt <ehaupt@FreeBSD.org> wrote: > > > Usually when I find that a port can't fetch the according distfile I > > simply google for the distfile with the following search string > > (e.g. for rsync): > > > > intitle:"index of" rsync-3.0.7.tar.gz > > > > This approach almost always delivers plenty of results. I then > > manually download one of the results into my DISTDIR and restart the > > normal build process > > How often do you actually do this? Whenever I have a problem with a > distfile it's normally a rerolled file that's been propagated to all > mirrors. Unfortunately, recently much more often. Especially with non default OPTIONS that pull in additional patches/distfiles. Emanuel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100722200635.7f54c356.ehaupt>