From owner-freebsd-hubs@FreeBSD.ORG Wed Jan 21 18:43:09 2004 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53D3816A4CE for ; Wed, 21 Jan 2004 18:43:09 -0800 (PST) Received: from luna.rtfmconsult.com (luna.rtfmconsult.com [202.83.72.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8163B43D31 for ; Wed, 21 Jan 2004 18:43:07 -0800 (PST) (envelope-from jason@rtfmconsult.com) Received: by luna.rtfmconsult.com (Postfix, from userid 42) id 9313F48F3F; Thu, 22 Jan 2004 12:43:06 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by luna.rtfmconsult.com (Postfix) with ESMTP id 8A91E52D17; Thu, 22 Jan 2004 12:43:06 +1000 (EST) Date: Thu, 22 Jan 2004 12:43:06 +1000 (EST) From: jason andrade To: Kris Kennaway In-Reply-To: <20040122023736.GA47498@xor.obsecurity.org> Message-ID: References: <20040122014706.GA46878@xor.obsecurity.org> <20040122023736.GA47498@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hubs@freebsd.org Subject: Re: freebsd 4.9 alpha ports link points into i386 tree ? X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 02:43:09 -0000 On Wed, 21 Jan 2004, Kris Kennaway wrote: > > separate release tree. > > > > so should the actual behaviour on disk be: > > > > o ports directory in releases/i386/X.X-RELEASE/ > > o symlink from releases/$arch/X.X-RELEASE/ports to point back into the > > i386 ports directory of the same release ? > > Isn't that what you described? nope. and this is getting confusing. to start again every architecture and release (4.X, 5.X) on ftp-master* has a separate ports directory. EXCEPT alpha/4.9-RELEASE/ports - which is a symlink to the i386/4.9-RELEASE/ports if the ports directory is identical for all architectures within a release (i am assuming it is not across the releases) then all but the alpha/4.9-RELEASE is broken as they all shouldn't have separate directories - there should be just one directory in the i386 tree which everything else links back into. if the ports directory is *not* identical then everything is fine except for the alpha/4.9-RELEASE which is pointing into a different architecture's ports directory. regards, -jason