From owner-freebsd-ports Thu Sep 9 19:42:29 1999 Delivered-To: freebsd-ports@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5D08815CDD; Thu, 9 Sep 1999 19:42:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 502B01CD8D3; Thu, 9 Sep 1999 19:42:28 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Sep 1999 19:42:28 -0700 (PDT) From: Kris Kennaway To: John Baldwin Cc: Bert Manchee , freebsd-ports@FreeBSD.org Subject: RE: Socks5 download In-Reply-To: <0FHS00KRENS54K@gkar.cc.vt.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 9 Sep 1999, John Baldwin wrote: > On 09-Sep-99 Bert Manchee wrote: > > If the current branch of the ports collection is requiring > > socks5-v1.0r9.tar.gz, why is it not available anywhere. it doesn't > > exist on your website, although there's a link to it. and on the NEC > > site supporting the socks5 server, they only offer socks5-v1.0r10.tar. > > gz - revision 10 instead of 9. what am i to do about this??? > > please help. The license terms for the NEC socks package prevent us from hosting the distfile elsewhere, so you have to fetch it manually (& register for it in the process). This means that when they upgrade to a new version it breaks the port, since the MD5 checksum changes, at a very least. You should contact the maintainer of the port (the MAINTAINER= line in /usr/ports/net/socks5) and see whether he is preparing an updated port. In the meantime, you can try fetching the distfile by hand as explained when you do a 'make' in /usr/ports/net/socks5 (which you will have to do anyway), and edit the Makefile to refer to the new filename. Then do a "make NOCHECKSUM=true install clean". If the new version doesn't compile out-of-the box, or any patches for the previous version fail to apply, you'll have to build it by hand. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message