From owner-freebsd-questions@FreeBSD.ORG Thu Apr 6 00:47:35 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 357B116A400 for ; Thu, 6 Apr 2006 00:47:35 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE1A643D46 for ; Thu, 6 Apr 2006 00:47:34 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 08B31D4748F for ; Wed, 5 Apr 2006 20:47:33 -0400 (EDT) Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Wed, 05 Apr 2006 20:47:23 -0400 X-Sasl-enc: 9eM13tuYC08SUevQWtEZKgMSocsSrDWRX2k41zvPLDcx 1144284443 Received: from bb-87-81-140-128.ukonline.co.uk (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by frontend3.messagingengine.com (Postfix) with ESMTP id 15F2C2319 for ; Wed, 5 Apr 2006 20:47:22 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Thu, 6 Apr 2006 01:47:28 +0100 User-Agent: KMail/1.9.1 References: <200604050035.k350Z9cP098258@app.auscert.org.au> In-Reply-To: <200604050035.k350Z9cP098258@app.auscert.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604060147.30726.list-freebsd-2004@morbius.sent.com> Subject: Re: How to handle 'local' ports/packages? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 00:47:35 -0000 On Wednesday 05 April 2006 01:35, freebsd-questions@auscert.org.au wrote: > to the +CONTENTS file for the package, but then portmanager complains that > it is nonexistent and won't complete 'portmanager -s'. To make matters > more awkward, this package is built from a closed-source binary > distribution and thus can't be properly ported, so I can't set it up > properly. A port does not have to be built from source, there are several (maybe many) closed-source packages in the ports-tree, for example: archivers/rar mail/mulberry x11/nvidia-driver