broken port: gnuchess

Conrad J. Sabatier conrads at
Mon Jan 17 00:32:40 PST 2005

On Mon, 17 Jan 2005 02:12:29 -0600, "Conrad J. Sabatier"
<conrads at> wrote:

> On Sun, 26 Dec 2004 12:39:05 -0800, Joshua Tinnin
> <krinklyfig at> wrote:
> > 
> > Yes, I'd like to make it clear I was also trying to help. The
> > Makefile
> > 
> > for gnuchess has this line:
> > 
> > MAINTAINER=     ports at
> 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 J. Sabatier <conrads at> -- "In Unix veritas"

More information about the freebsd-ports mailing list