Date: Sat, 9 Sep 2000 12:46:08 -0700 (PDT) From: Kelly Yancey <kbyanc@posi.net> To: SADA Kenji <sada@bsdclub.org> Cc: jim@thehousleys.net, freebsd-ports@FreeBSD.org Subject: Re: ports/18777: New Port: misc/upclient4 www.uptimes.net client Message-ID: <Pine.BSF.4.21.0009091238390.9118-100000@gateway.posi.net> In-Reply-To: <200009051104.UAA15876@home.bsdclub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Sep 2000, SADA Kenji wrote: > In article <200009041140.EAA16516@freefall.freebsd.org> > > You have to get maintainer's approval before you rewrite this line. > Please discuss it with current maintainer if you want to be new maintainer. > > And I want to know current maintainer's idea about this upgrade. > Hello Kelly Yancey, your upclient port is marked broken now > and we are planning to upgrade its version and unbreak it. > How do you think about this ? > My rational behind marking the port broken was 2-fold: 1. The current port didn't work anymore and 2. The new version of the software required compile-time configuration. There was actually some discussion on -hackers a long time ago (when I marked the port broken) about someone, possibly myself, adding a config file or getopt support to upclient. Obviously myself and others haven't found the spare cycles. :( It is my opinion that compile-time configuration is unacceptable for ports, but if James wants to take maintainership of the port, then my opinion wouldn't much matter. :) Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA Senior Engineer, Backplane, Inc. http://www.backplane.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009091238390.9118-100000>