Date: Tue, 3 Jul 2001 19:26:12 -0400 (EDT) From: ahd@kew.com To: FreeBSD-gnats-submit@freebsd.org Subject: ports/28678: portcheckout doesn't allow flexible build targets Message-ID: <20010703232612.D7F38BA5C@minerva.uucp.kew.com>
next in thread | raw e-mail | index | archive | help
>Number: 28678 >Category: ports >Synopsis: portcheckout doesn't allow flexible build targets >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: Tue Jul 03 16:30:03 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Drew Derbyshire >Release: FreeBSD 4.3-RELEASE i386 >Organization: Kendra Electronic Wonderworks, Stoneham MA 02180 (http://www.kew.com) >Environment: System: FreeBSD minerva.hh.kew.com 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Sat Jun 23 09:50:15 EDT 2001 root@:/usr/scratch/obj/usr/src/sys/MINERVA i386 Using portcheckout-2.0 on FreeBSD 4.3 >Description: portcheckout only supports the make targets "install clean" and "fetch". This reduces its usefullness since building other targets (such as "package", "reinstall", or omitting the "clean") requires moving above the ports directory, running portcheckout, and then moving into each port's directory and running the target. >How-To-Repeat: Use portcheckout to build anything other "install/clean" or "fetch" >Fix: It's not suggested that portcheckout have explicit support for every target that bored system admins can write PR's on, but rather a single option be added via which the person building the package can specify an arbitary string used as the make target. This might look like: portcheckout --target="package" package-name ... >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?20010703232612.D7F38BA5C>