From owner-freebsd-ports@FreeBSD.ORG Sun Jan 15 03:38:41 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FF2C16A41F for ; Sun, 15 Jan 2006 03:38:41 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF3DE43D46 for ; Sun, 15 Jan 2006 03:38:40 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.101] (adsl-65-65-114-198.dsl.rcsntx.swbell.net [65.65.114.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 6D691114327 for ; Sat, 14 Jan 2006 21:39:47 -0600 (CST) Date: Sat, 14 Jan 2006 21:37:43 -0600 From: Paul Schmehl To: freebsd-ports@freebsd.org Message-ID: X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Optional patching? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2006 03:38:41 -0000 I have an interesting situation. I maintain the security/barnyard port. It's used for several things, one of which is sguil. (I'm working on new ports for that as well.) Barnyard includes a plugin for sguil, named op_sguil.plugin. The sguil developers have changed the way they gather data for the newest release, 0.6.x. The new release requires that you patch barnyard to update the op_sguil.plugin. However, people who are still running the older versions of sguil; 0.5.x cannot use the new, patched version of the op_sguil.plugin. My question is, is it possible to make a patch optional? Offer the user the choice of patching or not based upon what version of sguil they intend to install? If it is, how would the sguil port (which requires barnyard) patch barnyard if barnyard had been previously installed without the patch? Is this something that can be done within the port? Or should it just be in pkg-message and let the user deinstall and reinstall and patch barnyard? Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/