From owner-freebsd-ports Fri Aug 7 14:55:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03158 for freebsd-ports-outgoing; Fri, 7 Aug 1998 14:55:11 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03141; Fri, 7 Aug 1998 14:54:57 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca9-112.ix.netcom.com [209.109.236.112]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id OAA16616; Fri, 7 Aug 1998 14:54:36 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id OAA23142; Fri, 7 Aug 1998 14:54:33 -0700 (PDT) Date: Fri, 7 Aug 1998 14:54:33 -0700 (PDT) Message-Id: <199808072154.OAA23142@silvia.hip.berkeley.edu> To: mph@FreeBSD.ORG CC: freebsd-ports@FreeBSD.ORG In-reply-to: <199808061801.LAA17607@freefall.freebsd.org> (message from Matthew Hunt on Thu, 6 Aug 1998 11:01:12 -0700 (PDT)) Subject: Re: ports/7495 From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * - Removed x11 from CATEGORIES line; it only needs to be there if * the port would logically fit into /usr/ports/x11 (which is being * split up, anyway). As of yesterday or so, USE_X11=yes is the * way to say a port needs X libraries. I've got an impression that reusing the USE_X11 variable was a bad idea. For things that were already in the tree, it was a simple renaming, but when we have new ports coming in with USE_X11, it might be too much trouble to check if it's actually USE_X11 or it means USE_X_PREFIX. How about we change the name of this variable before it's used? (I can even add a check in bsd.port.mk to print a warning if it's defined.) What do people think about USE_XLIB or USE_LIBX? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message