Date: Thu, 2 Sep 2004 21:44:38 GMT From: Colin Henein <freebsdpr@cmh.parliant.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/71314: Impossible to know which WITH_* variables are available for a port Message-ID: <200409022144.i82LicPZ036457@www.freebsd.org> Resent-Message-ID: <200409022150.i82LoLgX098297@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 71314 >Category: ports >Synopsis: Impossible to know which WITH_* variables are available for a port >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Sep 02 21:50:21 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Colin Henein >Release: 4.10 >Organization: Parliant Corp. >Environment: FreeBSD silk-new.parliant.com 4.10-RELEASE FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004 root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: Many ports offer compile-time variations based on things like ENABLE_SUIDPERL etc. Generally you only find out you needed one of these once you've installed the software and it doesn't work, or when compilation fails. This is very frustrating. >How-To-Repeat: Try to install some ports that you've never used before >Fix: The standards for porters should be changed to require an "INFO" file, or "make info" or something standard that gives some guidance about how to build the port using the right options depending on what you want. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409022144.i82LicPZ036457>