On 10/03/14 18:27, Antoine Jacoutot wrote:
> Hi.
>
> So, to all of you slackers out there who are wondering how you could
> contribute to the project, have a look at:
> http://portroach.openbsd.org/
>
> This will let you know the ports that could use an update in our tree. The
> point is not to *blindly* update everything of course, but at least it will
> give you a chance to look at candidates (full disclosure: there are many!).
> The "the openbsd ports mailing-list" MAINTAINER references all orphan ports,
> so it's likely there's some nice work to do in there -- some of which may be
> very trivial.
>
> Oh also, a nice side effect is that you can start pointing fingers at
> maintainers that are slacking too much :-)
>
> Do note that portroach[1] is still a fast moving target: you can harass
> jasper@ about the bugs you find...
>
> If you are maintaining a port and would like portroach to automatically send
> you a mail when one of your port becomes out-of-date, drop me a mail and I'll
> register you.
> This will allow you to update it before anyone has a chance to mock you for
> being out-of-date!
>
> [1]
> portroach is a friendly fork of FreeBSD's portscout
>
p5-Data-AMF - needs a maintainer change, so I am listed once only...
p5-AMF-Connection, p5-Storable-AMF, p5-IO-Socket-Socks, p5-IO-HTML,
p5-LWP-Protocol-socks already updated latest should be in openbsd-wip.
p5-LWP-Protocol-socks - requires all the p5-libwww updates
RUN_DEPENDS = security/p5-IO-Socket-SSL>=0.96 \
net/p5-IO-Socket-Socks>=0.2 \
www/p5-libwww>=6.02 \
www/p5-LWP-Protocol-https>=6.02
Current p5-libwww version I have is now at 6.08, recently updated to
this version, needs runtime testing, everything should be upto date in
openbsd-wip.
The other 3 ports I will look at, I have a later sleuthkit 4.1.2 port
but is not in openbsd-wip, need to update to 4.1.3.
Can you add me to the mail list.
