Date: Mon, 17 Jan 2005 02:32:32 -0600 From: "Conrad J. Sabatier" <conrads@cox.net> To: freebsd-ports@freebsd.org Cc: h <h@erathia.be> Subject: Re: broken port: gnuchess Message-ID: <20050117023232.56447133@dolphin.local.net> In-Reply-To: <20050117021229.1e8b42ee@dolphin.local.net> References: <200412231651.52690.h@erathia.be> <20041226132723.GI1435@k7.mavetju> <200412261512.50849.h@erathia.be> <200412261239.06078.krinklyfig@spymac.com> <20050117021229.1e8b42ee@dolphin.local.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Jan 2005 02:12:29 -0600, "Conrad J. Sabatier" <conrads@cox.net> wrote: > On Sun, 26 Dec 2004 12:39:05 -0800, Joshua Tinnin > <krinklyfig@spymac.com> wrote: > > > > Yes, I'd like to make it clear I was also trying to help. The > > Makefile > > > > for gnuchess has this line: > > > > MAINTAINER= ports@FreeBSD.org > > It shouldn't. I recently took over the maintenance of this port, and > the Makefile *should* reflect this. Are you perhaps trying to build > and outdated, broken version of this port? > > The MAINTAINER line *should* show my e-mail address, if your ports > tree is up to date. And, in another followup in this thread, I also wrote: > Is everything OK now with this port? > > I'm really sorry for not responding sooner, but I've been very, very > busy lately. If there are still some outstanding issues, I'll see > what I can do. > > I have to say, I was really quite surprised to learn that people were > having problems with this port. It all seemed to be A-OK when I > submitted that last update. I only just now finally got around to checking this thing out (sorry for the lag), and I see that it is indeed broken. I'll try to get it worked out ASAP. My apologies. I must have forgotten to test the fetch/extract stages when I was putting the port together. I'll have to remember not to make *that* mistake again in the future. :-) Still, it's very odd; I don't recall seeing the pathnames with the double slashes before. Just off the top of my head, I really don't know what's happening with this port at the moment. But it *will* be fixed, rest assured. :-) Again, sorry for not getting back on this thing sooner. Conrad -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050117023232.56447133>