From owner-freebsd-ports Wed Oct 7 15:30:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09989 for freebsd-ports-outgoing; Wed, 7 Oct 1998 15:30:49 -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 PAA09921 for ; Wed, 7 Oct 1998 15:30:17 -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 PAA19447; Wed, 7 Oct 1998 15:30:08 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id PAA11377; Wed, 7 Oct 1998 15:30:05 -0700 (PDT) Date: Wed, 7 Oct 1998 15:30:05 -0700 (PDT) Message-Id: <199810072230.PAA11377@silvia.hip.berkeley.edu> To: n@nectar.com CC: ports@FreeBSD.ORG In-reply-to: (message from Jacques Vidrine on Wed, 07 Oct 1998 17:20:26 -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 * Point me to the documentation in question and I'd be glad to * add a paragraph or two about keeping up with ports if it appears * to be needed. www.freebsd.org/ports www.freebsd.org/handbook/ports.html come to mind. * Hmm, now I get why NetBSD has their makefiles as part of the * collection rather than part of the base system. That has its problems too.... Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message