From owner-freebsd-hackers Thu Apr 22 23:36: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [206.205.41.245]) by hub.freebsd.org (Postfix) with ESMTP id B0AC415A4F for ; Thu, 22 Apr 1999 23:35:45 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id CAA03618; Fri, 23 Apr 1999 02:32:18 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Fri, 23 Apr 1999 02:32:18 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: W Gerald Hicks Cc: Steve Kargl , freebsd-hackers@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: revisiting Motif policy in ports In-Reply-To: <199904230145.VAA74106@bellsouth.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999, W Gerald Hicks wrote: > How about a new DEPENDS_MOTIF (supplied by a port) which might > build Lesstif if HAVE_MOTIF is not set? > > I agree that Lesstif has become useful. (former skeptic) Maybe something a little more flexible. How about replacing REQUIRES_MOTIF with MOTIF_REQUIREMENTS and use the values MOTIF and LESSTIF. Then in the make.conf the users could define HAVE_MOTIF and/or HAVE_LESSTIF as necessary. What I'm getting at here is if Lesstif is a weaker version of Motif that may not work for every package, we should treat the requirements as ranging from strong (true Motif) to weak (works with Lesstif). Of course no one's going to test everything with Lesstif immediately. But as packages are known to work well enough, the requirements can be relaxed. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message