From owner-freebsd-ports@FreeBSD.ORG Mon Sep 22 14:52:22 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A155216A4B3 for ; Mon, 22 Sep 2003 14:52:22 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-107-253.dsl.lsan03.pacbell.net [64.169.107.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7F5E43FF3 for ; Mon, 22 Sep 2003 14:52:19 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 5EA6666E05; Mon, 22 Sep 2003 14:52:19 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 48043AC7; Mon, 22 Sep 2003 14:52:19 -0700 (PDT) Date: Mon, 22 Sep 2003 14:52:19 -0700 From: Kris Kennaway To: fgudin@nerim.net Message-ID: <20030922215219.GA48239@rot13.obsecurity.org> References: <1931.213.41.170.5.1064248841.squirrel@webmail.nerim.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: <1931.213.41.170.5.1064248841.squirrel@webmail.nerim.net> User-Agent: Mutt/1.4.1i cc: freebsd-ports@freebsd.org Subject: Re: ports-wide config caching questions X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 21:52:22 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 22, 2003 at 06:40:41PM +0200, fgudin@nerim.net wrote: > Hi ports gurus ! >=20 > Learning about autoconf, it made me think that perhaps my 486 (!) would > benefit much from having a rather persistent config.cache for the whole > ports tree. Googled a bit about it, to nothing much interesting... > Hence my questions to you, my friends : 1st of all, is it wise, i.e. > there will be times when a cache reset will become necessary, how to > determine it ? > 2nd part : didn't see any knob for this is our .mk, do you see anything > else i might try to achieve this ? I expect that this wouldn't work very well, because there's no guarantee of consistency between applications that use gnu configure. The results of one configure script cannot necessarily be used to drive another configure script. Kris --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/b28TWry0BWjoQKURAlWeAJ9mgh1MFbj0sOdzLjTBaomH2sIBxgCbBjKZ WZhRw3hnl5YKWagMz5DZJkI= =66pb -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp--