Date: Tue, 27 Dec 2005 13:18:25 -0800 (PST) From: "Freddie Cash" <fcash@ocis.net> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: FreeBSD AMD list <freebsd-amd64@freebsd.org> Subject: Re: Sharing /usr/ports between AMD64 and I386 ok? Message-ID: <63677.24.71.129.36.1135718305.squirrel@imap.sd73.bc.ca> In-Reply-To: <20051227202546.GS63497@over-yonder.net> References: <cone.1135713305.795857.75924.5001@35st-server.simplicato.com> <1135714847.83838.34.camel@localhost> <20051227202546.GS63497@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, Dec 27, 2005 at 09:20:47PM +0100 I heard the voice of > Pav Lucistnik, and lo! it spake thus: >> Francisco Reyes p??e v ?t 27. 12. 2005 v 14:55 -0500: >>> Is /usr/ports the same for AM64 and I386? >> The FreeBSD Ports Collection is one and the same across all the >> releases and architectures. > Just make sure you scrupulously `make clean`, or sooner or later > you'll end up installing a dependancy on the wrong architecture. Not > that I've ever done such a thing, you understand... NFS mount /usr/ports from the central server, but set the work directory prefix (WRKDIRPREFIX) to something local so that all disk writes (tarball extracts, patching, compiling, etc) is done on the local system. That way, you can do multiple port compiles on separate systems without them stepping on each other's toes. And you don't have to worry about endianness, bitness, or anything else. -- Freddie Cash, LPIC-1 CCNT CCLP Helpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] fcash@sd73.bc.ca helpdesk@sd73.bc.ca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?63677.24.71.129.36.1135718305.squirrel>