From owner-freebsd-ports@FreeBSD.ORG Wed Oct 21 16:15:50 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D60C5106566B for ; Wed, 21 Oct 2009 16:15:50 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id A165D8FC0C for ; Wed, 21 Oct 2009 16:15:50 +0000 (UTC) Received: from localhost (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTPSA id 16819EBC0A; Wed, 21 Oct 2009 12:15:49 -0400 (EDT) Date: Wed, 21 Oct 2009 12:15:48 -0400 From: Bill Moran To: Paul Schmehl Message-Id: <20091021121548.8ae37fb5.wmoran@potentialtech.com> In-Reply-To: <65DDA3431A3A3C82B20A2039@utd65257.utdallas.edu> References: <20091021113121.fcdb99f5.wmoran@potentialtech.com> <65DDA3431A3A3C82B20A2039@utd65257.utdallas.edu> Organization: Bill Moran X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.5; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Subject: Re: Need advice from maintainers 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, 21 Oct 2009 16:15:50 -0000 In response to Paul Schmehl : > --On Wednesday, October 21, 2009 10:31:21 -0500 Bill Moran > wrote: > > > > > In response to Paul Schmehl : > > > >> I am the maintainer for security/barnyard2. This is an updated version of > >> security/barnyard, which I also maintain. The version of my port is the > >> current release version, but it has a really irritating problem that is fixed > >> in the current beta version. > >> > >> Barnyard2 is a program that parses snort logs and inserts them into a > >> database (mysql or postgresql). It is supposed to create a placemarker file > >> (called a waldo file) that maintains a record of what logs it has already > >> parsed. (This is only one way of using the program. There are others as > >> well.) The problem in the release version is that it does not read the > >> waldo file when the program is restarted. So every time you restart > >> barnyard2, it reinserts into the database every alert you still have log > >> files for. The beta version fixes this problem. > >> > >> I have created a port for the beta version and am using it myself, but I know > >> that using beta versions of software is frowned upon. Should I go ahead and > >> submit this port because it solves this problem? > >> > >> If I do, my thinking is that I should adjust the pkg-message file in the > >> existing port to warn the user about the problem and note that the beta > >> version solves it so they might want to consider using that instead. > > > > An option that you did not mention is to take the patch that fixes that > > single problem and include as a patch file for barnyard2. That way it's > > not a true beta, it just has that single patch to fix a known problem. > > > > For me, I think that would be the preferred method in this case. > > > > I *might* be able to do that, if I can figure out where in the code the problem > is fixed. I've had two semesters of C++, but I am not a programmer and > consider myself the rankest of novices wrt code. In a perfect world. you wouldn't have to be a C++ coder. In theory, you should be able to look at their SVN/CVS/git/whatever repository and find the commit that says it's fixed this problem, then just generate a diff between that version and the release version. Of course, that's in a perfect world. I'm not familiar with that project, so I don't know if they're that organized or not. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/