From owner-freebsd-ports Wed Oct 7 14:29:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26532 for freebsd-ports-outgoing; Wed, 7 Oct 1998 14:29:59 -0700 (PDT) (envelope-from owner-freebsd-ports@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 OAA26522 for ; Wed, 7 Oct 1998 14:29:52 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca3-63.ix.netcom.com [209.109.233.63]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id OAA19392; Wed, 7 Oct 1998 14:29:26 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id OAA11079; Wed, 7 Oct 1998 14:28:41 -0700 (PDT) Date: Wed, 7 Oct 1998 14:28:41 -0700 (PDT) Message-Id: <199810072128.OAA11079@silvia.hip.berkeley.edu> To: n@nectar.com CC: ports@FreeBSD.ORG In-reply-to: (message from Jacques Vidrine on Wed, 07 Oct 1998 12:02:06 -0500) Subject: Re: What's the right way to handle old bsd.port.mk? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * What should a port that needs to know PORTOBJFORMAT do on a system * with an older bsd.port.mk? Nothing. Ports shipped with releases go out with matching bsd.port.mk's; people using ports-current are expected to get the latest bsd.port.mk. The latter part is becoming more of a problem lately; maybe if you can go look into documentation to make it clearer, it will be a much better use of your time IMO. :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message