Date: Mon, 3 Jan 2000 14:19:24 -0500 (EST) From: kbyanc@posi.net To: FreeBSD-gnats-submit@freebsd.org Subject: ports/15865: update to upclient port Message-ID: <200001031919.OAA15832@kronos.alcnet.com>
next in thread | raw e-mail | index | archive | help
>Number: 15865 >Category: ports >Synopsis: update to upclient port >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jan 3 11:20:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: Kelly Yancey >Release: FreeBSD 3.2-STABLE i386 >Organization: >Environment: >Description: The upclient port is broken. The version currently fetched is no longer supported. I cannot reasonably port the new version of the upclient (4.03) because it requires all of the configuration settings (of which there are 3 to 5 depending on one's network environment) to be compiled into the binary. When the author restores the ability to read the configuration from a config file (or even a command-line parameter), then I'll update the port to that version. Alas, it seems a port has died despite much work to be revived. So this PR is to bury it until the BROKEN flag can be unset. >How-To-Repeat: >Fix: diff -ru upclient.orig/Makefile upclient/Makefile --- upclient.orig/Makefile Mon Jan 3 13:38:39 2000 +++ upclient/Makefile Mon Jan 3 14:04:16 2000 @@ -13,6 +13,8 @@ MAINTAINER= kbyanc@posi.net +BROKEN= Client is outdated and new client cannot be reasonably ported + ALL_TARGET= bsd INSTALL_TARGET= bsd install CP=$(CP) >Release-Note: >Audit-Trail: >Unformatted: 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?200001031919.OAA15832>