From owner-freebsd-ports@FreeBSD.ORG Thu May 11 17:37:31 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C53716A524 for ; Thu, 11 May 2006 17:37:31 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from mail.ipt.ru (mail.ipt.ru [80.253.10.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id C21B243E19 for ; Thu, 11 May 2006 17:37:29 +0000 (GMT) (envelope-from bsam@ipt.ru) Received: from stat.sem.ipt.ru ([192.168.12.1] helo=srv.sem.ipt.ru) by mail.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1FeF6O-000DQk-K7; Thu, 11 May 2006 21:37:28 +0400 Received: from bsam by srv.sem.ipt.ru with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1FeF6h-000CvS-Vh; Thu, 11 May 2006 21:37:47 +0400 To: Frank Laszlo References: <00bd01c6750a$b7c631e0$0a1610ac@prodcave.com> <4463603F.3050600@vonostingroup.com> <39169750@srv.sem.ipt.ru> <44636F83.8020103@vonostingroup.com> From: Boris Samorodov Date: Thu, 11 May 2006 21:37:47 +0400 In-Reply-To: <44636F83.8020103@vonostingroup.com> (Frank Laszlo's message of "Thu, 11 May 2006 13:08:19 -0400") Message-ID: <07007716@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: ports@freebsd.org Subject: Re: tomcat55 port on AMD64 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 May 2006 17:37:32 -0000 On Thu, 11 May 2006 13:08:19 -0400 Frank Laszlo wrote: > You would think so, but the fact of the matter is, ARCH should be a (In my previous email I answered to this) > READONLY variable. It is relied upon heavily in the ports framework and > shouldn't be changed, ever. Why we don't just use another variable name > to do the trickery is what I am wondering. What can you say about bsd.linux-rpm.mk? It uses a new variable LINUX_RPM_ARCH and doesn't rewrite ARCH. Unfortunately, linux_base-* ports can't use it (a chicken and egg problem). That's why any linux-* port using b.l.m _and_ linux_base-fc3 shouldn't have the problem you are speaking of. WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone & Internet Service Provider