Date: Tue, 12 Apr 2011 01:21:28 +0400 From: Mikhail Tsatsenko <m.tsatsenko@gmail.com> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: update OpenVAS ports Message-ID: <BANLkTik6e=N0yHZ=KxRrZ5jpcSrkEb7=2w@mail.gmail.com> In-Reply-To: <4DA36B85.8000103@FreeBSD.org> References: <BANLkTimgMKrjSZ%2Bxq%2BSvrgK8dO7OQeh4xA@mail.gmail.com> <BANLkTimHcBfc2ig2fn7JAZdq8Pkg6Rhj1w@mail.gmail.com> <4DA35E6E.1020402@gmail.com> <4DA36B85.8000103@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/4/12 Doug Barton <dougb@freebsd.org>: > On 04/11/2011 13:02, Mikhail Tsatsenko wrote: >> >> On 11.04.2011 23:15, =EC=C0=C2=CF=CD=C9=D2 =E7=D2=C9=C7=CF=D2=CF=D7 wrot= e: >>> >>> No one is maintaining it so I am writing here. Current version in >>> ports is >>> 2.0 (very outdated). Current live version in 4.0. >>> >>> OpenVAS 4.0 is quite different so some of the old ports need to be >>> removed >>> or reworked. As of now in ports are these: >>> >>> security/openvas-client 2.0.4_2 >>> security/openvas-libnasl 2.0.1_2 >>> security/openvas-libraries 2.0.3 >>> security/openvas-plugins 1.0.7_2 >>> security/openvas-server 2.0.2_2 >>> >> I'd like to take mainteinership of these ports. > > Given how out of date they are, IMO changing maintainer should be include= d > in patches that actually update them (and/or provide suitable replacement= s > for the new version). Others may have different ideas though. > > Fine, I'll submit a PR when patches will be ready. -- Mikhail
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTik6e=N0yHZ=KxRrZ5jpcSrkEb7=2w>