From owner-freebsd-ports@freebsd.org  Tue Jul 12 10:43:25 2016
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D068B93354
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Tue, 12 Jul 2016 10:43:25 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 333D315DE
 for <freebsd-ports@freebsd.org>; Tue, 12 Jul 2016 10:43:25 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1bMv9v-0008uy-LR; Tue, 12 Jul 2016 12:43:23 +0200
Date: Tue, 12 Jul 2016 12:43:23 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: "Danilo G. Baio" <dbaio@bsd.com.br>
Cc: freebsd-ports@freebsd.org
Subject: Re: security/w3af update
Message-ID: <20160712104323.GG95302@home.opsec.eu>
References: <CAKZCxeX241-ggomApQXF1rGwE7a8XAk8-xr5oCp7P5bCKOmUQw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKZCxeX241-ggomApQXF1rGwE7a8XAk8-xr5oCp7P5bCKOmUQw@mail.gmail.com>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2016 10:43:25 -0000

Hi!

> I wrote an update for security/w3af and the hole was deeper than I thought.

Thanks! That looks very interesting!

> It was necessary several new ports as dependency:
[...]
> I did not open a PR yet... I am wondering if is better open a new PR for
> each dependency or just one PR for security/w3af, anyone could help ?

If you create PRs for each depend and link them to the main PR for
the security/w2af update, that would be the recommended way.

> There are still a few issues to be resolved and plugins to be tested. This
> happens with me too:
> https://github.com/andresriancho/w3af/issues/13636
> 
> The patch is here:
> http://dbaio.bs2cloud.com.br/FreeBSD/w3af/w3af_1.6.49.patch

If you can add that patch to the port ?

-- 
pi@opsec.eu            +49 171 3101372                         4 years to go !