Date: Tue, 27 Oct 1998 07:28:28 +0100 From: Andreas Klemm <andreas@klemm.gtn.com> To: Joseph Koshy <jkoshy@FreeBSD.ORG>, Satoshi Asami <asami@FreeBSD.ORG> Cc: cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: ports/misc/tet Makefile Message-ID: <19981027072828.A26596@klemm.gtn.com> In-Reply-To: <199810270157.RAA23260@hub.freebsd.org>; from Joseph Koshy on Mon, Oct 26, 1998 at 05:57:21PM -0800 References: <199810260838.AAA05993@silvia.hip.berkeley.edu> <199810270157.RAA23260@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 26, 1998 at 05:57:21PM -0800, Joseph Koshy wrote: > sa> Also, you should just make TET_ROOT a compilation option unless > sa> there's a very good reason not to do so. The spirit of ports > sa> collection is to have a "canned" configuration that is easy to use, > > I'll look into this. Some of the publically available test suites > that use TET (eg:- the Opengroup POSIX96 suite) install under $TET_ROOT > and have specific requirements for $TET_ROOT; moderately large amounts of > disk space being one of them, a r/w permissions for non-root uids being > another. They could easily use symbolic links to do the following cd /usr/local cp -rp /usr/local/tet/* /largefs rm -rf tet ln -s /largefs tet I do this for example with the squid port. Or they should get a hook in the port, so that they can build the port with make TET_DIR=/someplace And if BATCH mode is enabled we default to /usr/local/tet or whatever (didn't look at the port exactly). But this would be doable without too much work I think. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981027072828.A26596>