From owner-freebsd-ports Wed Feb 18 21:29:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06826 for freebsd-ports-outgoing; Wed, 18 Feb 1998 21:29:04 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from silvia.HIP.Berkeley.EDU (ala-ca34-51.ix.netcom.com [207.93.143.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06817 for ; Wed, 18 Feb 1998 21:28:59 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id VAA15807; Wed, 18 Feb 1998 21:09:30 -0800 (PST) Date: Wed, 18 Feb 1998 21:09:30 -0800 (PST) Message-Id: <199802190509.VAA15807@silvia.HIP.Berkeley.EDU> To: matt@zigg.com CC: ports@FreeBSD.ORG In-reply-to: (message from Matt Behrens on Wed, 18 Feb 1998 09:06:13 -0500 (EST)) Subject: Re: Jordan's challenge (imap-uw) From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * I could do that. I have some well-connected (four backbone connections) * http space. Ok. Then when you update the port, put your site at the beginning of the MASTER_SITES list and make sure you put a tarball that matches the md5 there. It may help if you can put it in a subdirectory (and change it every time), so when you send-pr a port upgrade and put up a new tarball, there won't be a time lag when there will be an inconsistency. Satoshi (sigh, all this trouble for authors who don't change filenames....) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message