From owner-freebsd-ports  Thu Jun  5 21:36:33 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA26202
          for ports-outgoing; Thu, 5 Jun 1997 21:36:33 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26197
          for <ports@freebsd.org>; Thu, 5 Jun 1997 21:36:30 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id VAA16559; Thu, 5 Jun 1997 21:36:15 -0700 (PDT)
Date: Thu, 5 Jun 1997 21:36:15 -0700 (PDT)
Message-Id: <199706060436.VAA16559@silvia.HIP.Berkeley.EDU>
To: james@nexis.net
CC: ports@freebsd.org, rdm@cfcl.com
In-reply-to: <Pine.BSF.3.95q.970606002814.17533H-100000@nexis.net> (message from James FitzGibbon on Fri, 6 Jun 1997 00:29:51 -0400 (EDT))
Subject: Re: first cut of multiple architecture support
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * Personally, I think that the main targets should be smart
 * enough to use defined variables rather than create an extra 10
 * or 12 targets per OS.

Well, one problem is that OPSYS and ARCH are not defined until you
read bsd.port.mk.  So you can't really do much in the port Makefile
(unless you put the targets after the ".include <bsd.port.mk>" line,
which will open a whole new can of worms).

Now that I thought more, I think this should be handled in the new
"Makefile.*" include files.  Please forget I ever mentioned this. ;)

Satoshi