Date: Tue, 2 Feb 2010 18:58:36 +0000 From: David Wood <david@wood2.org.uk> To: Nick Rogers <ncrogers@gmail.com> Cc: ports@freebsd.org, =?iso-8859-1?q?S=F8ren_Schr=F8der?= <soeren.schroeder@gmail.com> Subject: Re: FreeBSD Port: freeradius-2.1.6 Message-ID: <1Elu6rBcXHaLFAhr@wood2.org.uk> In-Reply-To: <147432021002020928t6f20d3f1l91707fa9fe3c878d@mail.gmail.com> References: <a5b802961002020646m5adc753p3f24f81f3b1d47d1@mail.gmail.com> <147432021002020928t6f20d3f1l91707fa9fe3c878d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear all, I must apologise for taking my eye off the ball with the FreeRADIUS port. I've been extremely busy recently, and am likely to remain rather busy for the next couple of months. A further complication is that I'm about to reformat and reinstall my FreeBSD server. I did put some work into the Perl problem and the libtool problem in the past, but didn't come up with fully working solutions. I'll attempt to look at your gzip urgently, Nick, also PR ports/143487, so that we can get the port working again. I'm aware too of utmp related breakage on 9-CURRENT, though that will probably have to wait for a while. pkg-plist is always a tricky file to get right for FreeRADIUS. I have a rather hacky shell script that parses a FreeRADIUS source tree and creates pkg-plist. Maybe I should place it online somewhere - so long as you all promise not to vomit. If it transpires that I can't give the port what it deserves in the medium to long term, I will look to relinquish maintainership, though I'm not quite to that point yet. If it does come to looking for a new maintainer, people should be aware that FreeRADIUS can be a very time consuming port to maintain. It has many files and a large number of dependencies. Once again, my apologies for the collective disappointment. Humbly yours, David -- David Wood david@wood2.org.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1Elu6rBcXHaLFAhr>