From owner-freebsd-ports Tue Oct 5 16:47:18 1999 Delivered-To: freebsd-ports@freebsd.org Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (Postfix) with ESMTP id 2E417156B6 for ; Tue, 5 Oct 1999 16:46:58 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: from bubble.didi.com (silvia [209.111.213.92]) by vader.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id QAA34896; Tue, 5 Oct 1999 16:44:54 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.9.3/8.8.8) id QAA06081; Tue, 5 Oct 1999 16:44:34 -0700 (PDT) (envelope-from asami) To: patl@phoenix.volant.org Cc: Will Andrews , ports@FreeBSD.ORG Subject: Re: FreeBSD Port: staroffice-3.1 References: From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 05 Oct 1999 16:44:33 -0700 In-Reply-To: patl@phoenix.volant.org's message of "Tue, 5 Oct 1999 15:24:28 -0700 (PDT)" Message-ID: Lines: 13 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: patl@phoenix.volant.org * Handle it the same way we do the Netscape 128-bit US version. * Make the user do the download manually; but have the port handle * dependancies and the actual installation. For the kernel dependancies * that can't be automated in the port, the port can issue a message * telling the user what they need to do. (Ideally, it would first * perform some sort of test to see if the running kernel was actually * missing the necessary features.) That sounds wonderful. :) -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message