From owner-freebsd-hubs@FreeBSD.ORG Wed Jan 21 18:54:43 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 3F41B16A4CE for ; Wed, 21 Jan 2004 18:54:43 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-67-119-53-122.dsl.lsan03.pacbell.net [67.119.53.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id B76A143D3F for ; Wed, 21 Jan 2004 18:54:41 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6931366CD1; Wed, 21 Jan 2004 18:54:38 -0800 (PST) Date: Wed, 21 Jan 2004 18:54:38 -0800 From: Kris Kennaway To: jason andrade Message-ID: <20040122025438.GA47642@xor.obsecurity.org> References: <20040122014706.GA46878@xor.obsecurity.org> <20040122023736.GA47498@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: hubs@freebsd.org cc: Kris Kennaway 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:54:43 -0000 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 22, 2004 at 12:43:06PM +1000, jason andrade wrote: > On Wed, 21 Jan 2004, Kris Kennaway wrote: >=20 > > > 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? >=20 > nope. and this is getting confusing. to start again >=20 > 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 >=20 > 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. >=20 > 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 p= orts > directory. OK, thanks for clarifying. As far as I know there only needs to be one copy of the checked-out ports collection per release, so the others can all be replaced with symlinks [1]. Kris [1] If someone is going to retrofit all the old releases on ftp-master, be careful, because from past experience, things like rsync and/or cvsup don't like it when you replace a directory with a symlink. --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFADztuWry0BWjoQKURAuEIAKCxG9SodrjQBevN79p/CFK/n44mGACeMNVm Lx/+gwb6YJ9NwL05bcyf7Hk= =4fNF -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO--