Date: Wed, 18 Jun 2014 01:23:43 +0200 From: Michael Gmelin <freebsd@grem.de> To: Marko =?UTF-8?B?Q3VwYcSH?= <marko.cupac@mimar.rs> Cc: freebsd-ports@freebsd.org Subject: Re: please help with fixing port Message-ID: <20140618012343.40aa5b71@bsd64.grem.de> In-Reply-To: <20140617155545.1b1eff0e9ee7f63b873c2357@mimar.rs> References: <20140617155545.1b1eff0e9ee7f63b873c2357@mimar.rs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Jun 2014 15:55:45 +0200 Marko Cupa=C4=87 <marko.cupac@mimar.rs> wrote: > Hi, >=20 > Some would say that net-p2p/linuxdcpp is not that important, but being > the only decent GUI nmdc/adc client in FreeBSD ports tree, I think it > deserves to be properly maintained. >=20 > Latest update broke this port. I have submitted bug report: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D190600 >=20 > Unfortunately, the only suggestion was to try and fix the port myself, > as there is no maintainer. >=20 > I have almost no experience in maintenance of ports, and no experience > at all with compiler errors, inclusion of headers etc. >=20 > If someone would be so kind in helping me fixing this port, or point > me in the right direction, I would be very grateful. >=20 > Regards, I took a look at it and fixed it, it builds on all supported releases on redports and starts ok on 10-RELEASE amd64 now. Could you please try yourself and verify? Patch in phabricator: https://phabric.freebsd.org/D236 - Michael p.s. I can't maintain the port since I'm not using it myself. Maybe you're up for the challenge and become the maintainer yourself? It's a steep learning curve, but people around here are helpful. --=20 Michael Gmelin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140618012343.40aa5b71>