From owner-freebsd-ports@FreeBSD.ORG Sat Apr 5 04:36:00 2008 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 2A41D106564A for ; Sat, 5 Apr 2008 04:36:00 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id 0CAF38FC16 for ; Sat, 5 Apr 2008 04:35:59 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (cpe-24-175-90-48.tx.res.rr.com [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id 25B0F65505 for ; Fri, 4 Apr 2008 23:35:59 -0500 (CDT) Date: Fri, 04 Apr 2008 23:35:59 -0500 From: Paul Schmehl To: freebsd-ports@freebsd.org Message-ID: <08BCD7E7030EE547F4F9C93B@Macintosh.local> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==========67539DB9FB83E8040FFF==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: New squil 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: Sat, 05 Apr 2008 04:36:00 -0000 --==========67539DB9FB83E8040FFF========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I'm the port maintainer for security/sguil-sensor, security/sguil-server and security/sguil-client. These ports go together and need to be updated together. At present, the version is 0.6.1.3. The new ports will be version 0.7.0 and have some very significant changes from the previous version. Also, I am the port maintainer of security/barnyard and the slave port security/barnyard-sguil6 port. I have some questions about how to do this update. Should I patch the existing ports? If I do, the committer would need to commit all three ports simultaneously or someone might install mis-matched versions. Should we rename the existing ports to sguil6-sensor -server and -client (or sguil-sensor6 - server6 -client6) and then install the new ones as new ports named as the present ones are? Should we rename the barnyard slave port to barnyard-sguil? I'm not sure what the best way is to proceed. A gzipped tarball of the three new ports is attached in case anyone wants to test them. Inside the tarball is gzipped tarballs of each of the three ports. DO NOT untar them in /usr/ports/security or you will overwrite the existing ports (which will then be overwritten in turn by your next c(v)sup). Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========67539DB9FB83E8040FFF==========--