From owner-freebsd-stable Thu Oct 29 20:26:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25643 for freebsd-stable-outgoing; Thu, 29 Oct 1998 20:26:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25637 for ; Thu, 29 Oct 1998 20:26:02 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sjx-ca115-43.ix.netcom.com [207.223.162.107]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id UAA15385; Thu, 29 Oct 1998 20:25:55 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id UAA19405; Thu, 29 Oct 1998 20:25:52 -0800 (PST) Date: Thu, 29 Oct 1998 20:25:52 -0800 (PST) Message-Id: <199810300425.UAA19405@silvia.hip.berkeley.edu> To: brett@peloton.physics.montana.edu CC: MillikS@salestech.com, freebsd-stable@FreeBSD.ORG In-reply-to: (message from Brett Taylor on Thu, 29 Oct 1998 14:07:38 -0700 (MST)) Subject: Re: Question about Ports Errors From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * You need to update your bsd.port.mk file. The easiest way to do this is Exactly. Using ports-current (aka ports-stable) without updating your bsd.port.mk is, um, not a good idea. ;) It is actually good that this thing (${PORTOBJFORMAT}) falls flat on its face, at least it tells the user that something is wrong. Otherwise you may not even know that there could be some problems. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message