Date: Fri, 22 Nov 2002 19:39:46 -0800 (PST) From: Kurt Werle <kwerle@pobox.com> To: FreeBSD-gnats-submit@FreeBSD.org Cc: kwerle@pobox.com Subject: ports/45613: make update doesn't Message-ID: <200211230339.gAN3dk6n041763@twoface.shiftmanager.net>
next in thread | raw e-mail | index | archive | help
>Number: 45613 >Category: ports >Synopsis: make update doesn't >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Nov 22 19:40:03 PST 2002 >Closed-Date: >Last-Modified: >Originator: Kurt Werle >Release: FreeBSD 4.7-RELEASE i386 >Organization: private >Environment: System: FreeBSD twoface.shiftmanager.net 4.7-RELEASE FreeBSD 4.7-RELEASE #1: Fri Nov 22 06:16:27 GMT 2002 root@twoface.shiftmanager.net:/usr/src/sys/compile/FIREWALL i386 >Description: cd /usr/ports make update Result: "Error: Please define either SUP_UPDATE or CVS_UPDATE first." OK, I'm an admin. I'll go dig up the damn cvsup info and jump the hoops, but this really ought to be trivial. If I do a make update from ports, I want to be walked through it automagically and never have to think about it ever again. When it does the walk it could easily create /usr/ports/updatescript that gets run every time I do make update. If I want to edit it, or toss it, I can. But please, do something automagically for me. Yeah, I'm a whiner. But this should be trivial. >How-To-Repeat: cd /usr/ports make update >Fix: >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?200211230339.gAN3dk6n041763>