On 10.02.2016 06:47, Peter Jeremy wrote:
On 2016-Feb-09 21:24:56 +0100, Kurt Jaeger <li...@opsec.eu> wrote:
Torsten wrote:
I did take a look. I could do both: maintaining the port and maintaining
the software. What do you need? ;)
Submit patches to the 12 PRs open for portmaster:
https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=portmaster
That is just being silly.
I'd start by triaging those bugs. One is clearly a kernel bug,
another maybe a bug in a different port and one is described as a
feature request. The remaining 9 may or may not still be bugs in
portmaster that are still relevant. Providing a patch for one of
the bugs would probably be sufficient for demonstrating interest
and ability.
The discussion also put some attention at the existing PRs. Walter
already tried to reproduce some of the PRs and give some feedback, for
example that an issue is not reproducibly at the current time. I think
this will be true for most of the PRs.
One already brings a patch with it. The first work will be most
management of the PRs.
I'm asking myself how to manage the code. Should i create a new GitHub
repository? Fork the existing from freebsd/portmaster? How to handle the
LOCAL Master-Site?
I submitted a PR to take maintainer-ship for portmaster:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207075
Also i fix some minor glitches and add missing RUN_DEPENDS.
Greetings,
Torsten
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
