ports/188895: OPTIONS_UNSET X11 doesn't seem to work

Vivek Khera vivek at khera.org
Tue Apr 22 17:40:01 UTC 2014


>Number:         188895
>Category:       ports
>Synopsis:       OPTIONS_UNSET X11 doesn't seem to work
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 22 17:40:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator:     Vivek Khera
>Release:        FreeBSD 9.2-RELEASE-p3 amd64
>Organization:
>Environment:
System: FreeBSD vk-dev.int.kcilink.com 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r260688: Wed Jan 15 12:29:34 EST 2014 khera at yertle.int.kcilink.com:/usr/obj/u/yertle1/sources/usr9/src/sys/KCI64 amd64


	
>Description:
	

I was running portupgrade today, and one of the updating ports was ImageMagick-nox11.

I saw warnings from ports that I was setting WITHOUT_X11=YES, and should instead
do OPTIONS_UNSET=X11.  I dutifully updated the make.conf file:

 OPTIONS_UNSET=GUI X11

and removed WITHOUT_X11 as well.

I restarted portmaster to have it pick up those new settings and it tried to
install ghostscript9 instead of using the installed ghostscript9-nox11. It
also tried to pull in a fair number of additional libraries that come with X11
support (possibly for some other ports I have).

>How-To-Repeat:
	

as above

>Fix:

	

keep using WITHOUT_X11 setting.
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-ports-bugs mailing list