Date: Wed, 21 Jan 2004 22:11:08 -0500 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: Kris Kennaway <kris@obsecurity.org> Cc: hubs@freebsd.org Subject: Re: freebsd 4.9 alpha ports link points into i386 tree ? Message-ID: <20040122031108.GB9102@electra.cse.Buffalo.EDU> In-Reply-To: <20040122025438.GA47642@xor.obsecurity.org> References: <Pine.GSO.4.50.0401221124120.4689-100000@luna.rtfmconsult.com> <20040122014706.GA46878@xor.obsecurity.org> <Pine.GSO.4.50.0401221231130.4689-100000@luna.rtfmconsult.com> <20040122023736.GA47498@xor.obsecurity.org> <Pine.GSO.4.50.0401221239110.4689-100000@luna.rtfmconsult.com> <20040122025438.GA47642@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 21, 2004 at 06:54:38PM -0800, Kris Kennaway wrote: > 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]. Things are the way they are mostly because of how releases get done I think. For the most part different people do the builds for the different architectures, post them to ftp-master at different times, etc. There tends to be more coordination for the 4.X releases because of only two architectures - fewer people involved. > [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. When compared to the sizes of everything else in the FTP site doing this might not be the best idea because it breaks being able to carry one specific architecture if the architecture you choose isn't the one with the "real" ports file. It does save us a little space but... -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040122031108.GB9102>