From owner-freebsd-alpha Thu Dec 31 08:51:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19203 for freebsd-alpha-outgoing; Thu, 31 Dec 1998 08:51:50 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19197; Thu, 31 Dec 1998 08:51:47 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id KAA30606; Thu, 31 Dec 1998 10:51:20 -0600 (CST) Date: Thu, 31 Dec 1998 10:51:20 -0600 (CST) From: Steve Price To: Narvi cc: Brian Handy , asami@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: Alpha ports collection? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 31 Dec 1998, Narvi wrote: # IMHO there should also be the NO_ALPHA (in general, NO_XXXX) which means # that the port is not applicapble to XXXX. After all, it is probable that # in some time there will be some ports specific to alpha, in which case # they would be marked NO_I386. # # The difference would be that BROKEN_XXXX would mean that the port is # broken and needs fixing, while NO_XXXX would mean that it is not # apllicable. # # IMHO it is a useful difference. I too like the idea of BROKEN_XXX, but I'd like to propose a little different tact for NO_XXX. The latter could easily get out of hand. Suppose we support ten archs, [A-J], and a port only works for A. We would have to have something along these lines in the port's Makefile. NO_B= yes NO_C= yes ... NO_J= YES Of course you could use ONLY_A, but what if it works for [A-D]. We have the same effect. How about we come up with something like this: EXCLUDE_ARCHS= B C D E F G H I J Or for the purist among us maybe the converse of this would be even better, since it wouldn't include archs we didn't know about or weren't yet known to work on. INCLUDE_ARCHS= A This would require us to add 'INCLUDE_ARCHS=i386' to every port currently in the tree, but that shouldn't be too painful. Comments? Maybe BUILD_ARCHS instead of INCLUDE_ARCHS? -steve # Sander, # this should probably be in -arch # # There is no love, no good, no happiness and no future - # all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message