From owner-svn-src-all@FreeBSD.ORG Thu Nov 17 19:16:50 2011 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18BDD1065674; Thu, 17 Nov 2011 19:16:50 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id CB1F88FC0C; Thu, 17 Nov 2011 19:16:49 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 61A6E46B0A; Thu, 17 Nov 2011 14:16:49 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E03F28A052; Thu, 17 Nov 2011 14:16:48 -0500 (EST) From: John Baldwin To: Ken Smith Date: Thu, 17 Nov 2011 14:16:47 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <201111151849.pAFInR3K012609@svn.freebsd.org> <201111171141.22648.jhb@freebsd.org> <1321551793.82271.55.camel@bauer.cse.buffalo.edu> In-Reply-To: <1321551793.82271.55.camel@bauer.cse.buffalo.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201111171416.47725.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 17 Nov 2011 14:16:49 -0500 (EST) Cc: Alexey Dokuchaev , src-committers@freebsd.org, Pawel Jakub Dawidek , svn-src-all@freebsd.org, David Chisnall , TAKAHASHI Yoshihiro , Nathan Whitehorn , svn-src-head@freebsd.org Subject: Re: svn commit: r227536 - in head: release share/man/man7 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2011 19:16:50 -0000 On Thursday, November 17, 2011 12:43:12 pm Ken Smith wrote: > On Thu, 2011-11-17 at 11:41 -0500, John Baldwin wrote: > > On Thursday, November 17, 2011 10:11:36 am Ken Smith wrote: > > > On Thu, 2011-11-17 at 14:57 +0000, Alexey Dokuchaev wrote: > > > > On Thu, Nov 17, 2011 at 09:44:52AM -0500, Ken Smith wrote: > > > > > This is the problem we are trying to "solve": > > > > > > > > > > Supported TARGET/TARGET_ARCH pairs for world and kernel targets > > > > > amd64/amd64 > > > > > arm/arm > > > > > arm/armeb > > > > > i386/i386 > > > > > ia64/ia64 > > > > > mips/mipsel > > > > > mips/mipseb > > > > > mips/mips64el > > > > > mips/mips64eb > > > > > mips/mipsn32eb > > > > > pc98/i386 > > > > > powerpc/powerpc > > > > > powerpc/powerpc64 > > > > > sparc64/sparc64 > > > > > > > > As I see it, for every pair except pc98/i386, second part should be used. > > > > For pc98/i386, first (pc98). Problem solved. ;-) > > > > > > > > ./danfe > > > > > > > > > > I'd still sort of prefer no special cases. However ... > > > > > > For the ISO / memstick filenames we could just program in `uname -p` > > > and ask the pc98 builder to modify the filenames post-build. But > > > we still have the dual names needed for the FTP site layout. There > > > it needs to be fully automated in the installer. > > > > > > So, given it seemed like we're sort of stuck with having the dual > > > names appearing in other places combined with it never causing us > > > to have special cases and/or conflicts it seemed like just biting > > > the bullet and having them in the ISO / memstick filenames too ... > > > > > > Have I mentioned I don't like any of the options? :-/ > > > > I think collapsing down to one name if uname -m == uname -p is not that > > terrible and would preserve the existing layout for most of the current > > cases (only pc98 would change, yes)? > > > > If you're referring to the FTP directory tree layout we wind up with: > > .../releases/amd64/9.0-RELEASE > .../releases/amd64/ISO-IMAGES/9.0 > > for an example of uname -m == uname -p. But for our two powerpc related > architectures we get: > > .../releases/powerpc/9.0-RELEASE > .../releases/powerpc/ISO-IMAGES/9.0 > .../releases/powerpc/powerpc64/9.0-RELEASE > .../releases/powerpc/powerpc64/ISO-IMAGES/9.0 > > I'm not sure I like the inconsistency. Given the available tradeoffs I prefer this to amd64/amd64. We could also define the rule another way, which is if a given TARGET only has a single TARGET_ARCH you just use TARGET, otherwise you use TARGET/TARGET_ARCH. (This can be parsed out of the output of 'make targets' fairly easily.) That would let you have: releases/amd64/9.0-RELEASE releases/powerpc/powerpc/9.0-RELEASE releases/powerpc/powerpc64/9.0-RELEASE -- John Baldwin