From owner-freebsd-ports Mon Mar 27 11:38:45 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA01731 for ports-outgoing; Mon, 27 Mar 1995 11:38:45 -0800 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 LAA01718 for ; Mon, 27 Mar 1995 11:38:36 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.9/8.6.9) id JAA18975; Mon, 27 Mar 1995 09:32:55 -0800 Date: Mon, 27 Mar 1995 09:32:55 -0800 Message-Id: <199503271732.JAA18975@silvia.HIP.Berkeley.EDU> To: mark@grondar.za CC: Ports@FreeBSD.org In-reply-to: <199503261921.VAA12963@grunt.grondar.za> (message from Mark Murray on Sun, 26 Mar 1995 21:21:43 +0200) Subject: Re: 2.1 ports testing (was Re: expect & majordomo requests (fwd)) From: asami@cs.berkeley.edu (Satoshi Asami/=?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) Sender: ports-owner@FreeBSD.org Precedence: bulk * How about asking the "owners" to test their code on a particular day (or * close) and datestamp that? * * OK, I know some folks have a lot of ports, and some don't do much * maintaining, but those who do their bit can take off the load. That's a good idea, but I think it's even better if we ask someone other than the "owner" to test the ports. The owner might have some special setup on his machine that others don't, or may overlook a stumbling block on the installation script (that he wrote), or...well you get the idea. So, people using ports, try to get the latest version, try to recompile everything on your computer and see how it goes! Oh, and don't forget to upgrade to the latest bsd.port.mk, it has been changing a lot lately! (I have made another major change concerning "official" patches, which I'm going to commit as soon as freefall comes back....) Satoshi