From owner-freebsd-ports Mon Mar 11 3:51:33 2002 Delivered-To: freebsd-ports@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 0BFDC37B402 for ; Mon, 11 Mar 2002 03:51:29 -0800 (PST) Received: (from sue@localhost) by phoenix.welearn.com.au (8.11.6/8.11.6) id g2BBpPC00558 for freebsd-ports@freebsd.org; Mon, 11 Mar 2002 22:51:25 +1100 (EST) (envelope-from sue) Date: Mon, 11 Mar 2002 22:51:25 +1100 From: Sue Blake To: freebsd-ports@freebsd.org Subject: handling static filenames Message-ID: <20020311225125.B96107@welearn.com.au> Mail-Followup-To: Sue Blake , freebsd-ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm working on four ports (2 down, 2 to go) that have source archives which do not change name when they are upgraded. How do we deal with this? Keep a copy of foo.zip somewhere else, renamed to foo-1.23.zip and list it in the Makefile instead of or as well as the author's site? I could plonk them under people.freebsd.org but I don't know that it's the right way to handle the situation. Do we have any precedents or battle scars? -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message