Date: Mon, 27 Aug 2001 21:49:07 -0700 From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> To: ijliao@FreeBSD.org Cc: Cy.Schubert@uumail.gov.bc.ca, freebsd-ports@FreeBSD.org, freebsd-security@FreeBSD.org Subject: Re: ports/29137: Brand New Tripwire-2.3.1 Port Message-ID: <200108280449.f7S4nxE03079@cwsys.cwsent.com> In-Reply-To: Your message of "Sat, 18 Aug 2001 00:36:40 PDT." <200108180736.f7I7ae119043@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200108180736.f7I7ae119043@freefall.freebsd.org>, ijliao@FreeBSD.org writes: > Synopsis: Brand New Tripwire-2.3.1 Port > > State-Changed-From-To: open->analyzed > State-Changed-By: ijliao > State-Changed-When: Sat Aug 18 00:35:13 PDT 2001 > State-Changed-Why: > why do we need separate ports for 1.2 (tripwire), 1.3.1 (tripwire-131) > and now 2.3.1 (tripwire-231) ? > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29137 > Originally 1.3.1 was created because it addressed some memory management issues and was a separate port the license was different enough to warrant it. Now that 2.3.1 is opensource, we can replace both 1.2 and 1.3.1 with 2.3.1. However Tripwire 1.2 and 1.3.1 do not share the same config file format as 2.3.1. For the time being that would leave 1.x users out on the limb until they've converted to 2.3.1 -- unless of course they use the default config file that comes with the any of the ports. I'm open to suggestions. What does the list think? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD Ministry of Management Services Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108280449.f7S4nxE03079>