From owner-freebsd-ports Thu May 18 04:35:43 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA05275 for ports-outgoing; Thu, 18 May 1995 03:49:27 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA05267 for ; Thu, 18 May 1995 03:49:21 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id DAA06905; Thu, 18 May 1995 03:49:11 -0700 Date: Thu, 18 May 1995 03:49:11 -0700 Message-Id: <199505181049.DAA06905@silvia.HIP.Berkeley.EDU> To: taob@gate.sinica.edu.tw CC: freebsd-ports@FreeBSD.ORG In-reply-to: (message from Brian Tao on Thu, 18 May 1995 18:21:22 +0800 (CST)) Subject: Re: tcsh 6.06 From: asami@CS.Berkeley.EDU (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) Sender: ports-owner@FreeBSD.ORG Precedence: bulk * Yeah, that's what I was worried about. I thought the code freeze * was only applicable to the core FreeBSD distribution, not third-party * packages and ports (like tcsh). Um, I think I've been shouting about this pretty loudly for quite a while, are you sure your mail connection is okay? Actually my mails to you (that I tried to send you last night) didn't leave my machine for 20 hours, maybe you are having a network problem. Anyway, to reiterate, we are in code freeze for the ports tree too, only bug fixes and additions of new ports are allowed. Be careful about bug fixes though, some alleged "fixes" in the past few days were actually introduction of new bugs. ;) Upgrades are NOT allowed unless there is a really good reason to do so (the old version opens a glaring security hole, etc.) In particular, "the distfile isn't at the master site anymore" isn't a valid reason, 'cause we will have the old distfile on the CD-ROM. Making a port that doesn't package work is a bug fix of the best kind, by the way. :) Satoshi