From owner-freebsd-questions@FreeBSD.ORG Mon Aug 18 05:14:33 2003 Return-Path: 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 A18AB37B401 for ; Mon, 18 Aug 2003 05:14:32 -0700 (PDT) Received: from bloodwood.hunterlink.net.au (mail.hunterlink.net.au [203.12.144.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F1F443F3F for ; Mon, 18 Aug 2003 05:14:31 -0700 (PDT) (envelope-from boris@brooknet.com.au) Received: from [202.7.67.59] (as1-p59.mait.hunterlink.net.au [202.7.67.59]) h7ICET4s015887 for ; Mon, 18 Aug 2003 22:14:29 +1000 From: Sam Lawrance To: freebsd-questions@freebsd.org Content-Type: text/plain Message-Id: <1061208866.25279.20.camel@dirk.no.domain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 18 Aug 2003 12:14:26 +0000 Content-Transfer-Encoding: 7bit Subject: How to structure a port with plugins X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 12:14:34 -0000 Hi all, (please cc replies to me) I'm writing a port for multisync. Included in the source tarball are a bunch of plugins for synchronising with various devices and programs. Not everbody is going to want them all. There's no existing mechanism to automatically build some or all of the plugins. What is the best way to build the plugins? I've thought of the doing the following: - Have a separate port for each plugin, depend on the main port for the source. This sure makes creating the packing list a lot simpler. - Build the plugins from the main port based in WITH_xxxxx variables Now I think about it the first option seems better, but I'd like to hear what anybody thinks. Thanks, -Sam Lawrance.