From owner-freebsd-ports@FreeBSD.ORG Wed Jul 11 21:58:30 2012 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7D3F5106564A for ; Wed, 11 Jul 2012 21:58:30 +0000 (UTC) (envelope-from matt@conundrum.com) Received: from kaywinnit.conundrum.com (unknown [IPv6:2001:4900:1:213::40]) by mx1.freebsd.org (Postfix) with ESMTP id 438028FC0A for ; Wed, 11 Jul 2012 21:58:30 +0000 (UTC) Received: from chani.conundrum.com ([216.235.10.34]) by kaywinnit.conundrum.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1Sp4vU-00023q-Gc; Wed, 11 Jul 2012 21:58:28 +0000 From: Matthew Pounsett Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 11 Jul 2012 17:58:23 -0400 To: freebsd-ports@FreeBSD.org Message-Id: Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Cc: Subject: Creating a port as plugin for multiple other ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2012 21:58:30 -0000 Pardon the cryptic subject line. I couldn't think of a more concise way = to describe what I'm working on. I'm working on building a port of mod_gearman, a monitoring plugin for = Nagios and Icinga. Since the plugin might modify icinga or might = modify nagios, it has different possible install locations for some = support files, and different possible users as owners of those files. The question I have is about the best way to approach this. Is this = something that crops up often enough for there to be a standard (or even = just preferred) method? The two that come to mind are: 1) create two different ports (icinga-mod_gearman and = nagios-mod_gearman). I don't particularly like this one since it requires maintenance of = two different ports. 2) use options to select which system is being plugged into. It's not clear to me whether it's considered good practice to define = options that are mutually exclusive, or whether reading in of the = options file would be too late in the process for defining dependencies. Are there other options here? Any guidance on the best route to take? = Are there existing ports which are in the same situation that I can crib = from? Thanks for any pointers.=