From owner-freebsd-security@FreeBSD.ORG Mon Aug 11 14:53:09 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8ECE637B401 for ; Mon, 11 Aug 2003 14:53:09 -0700 (PDT) Received: from smtp.sw.oz.au (alt.aurema.com [203.217.18.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74B5943F3F for ; Mon, 11 Aug 2003 14:53:07 -0700 (PDT) (envelope-from vance@aurema.com) Received: from smtp.sw.oz.au (localhost [127.0.0.1]) by smtp.sw.oz.au with ESMTP id h7BLqnFS021191; Tue, 12 Aug 2003 07:52:49 +1000 (EST) Received: (from vance@localhost) by smtp.sw.oz.au id h7BLqlr2021080; Tue, 12 Aug 2003 07:52:47 +1000 (EST) Date: Tue, 12 Aug 2003 07:52:47 +1000 From: Christopher Vance To: Marcus Reid Message-ID: <20030811215247.GA14202@aurema.com> References: <44llu6v432.fsf@be-well.ilk.org> <20030811202841.GA29452@blazingdot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030811202841.GA29452@blazingdot.com> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) cc: freebsd@critesclan.com cc: freebsd-security@freebsd.org Subject: Re: statically compiled files left over after a 'make world' X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2003 21:53:09 -0000 On Mon, Aug 11, 2003 at 01:28:42PM -0700, Marcus Reid wrote: : It's a fairly time-consuming process, but on occasion I like to : do a 'make world DESTDIR=$D' where D is an optional install root, : and then compare the resulting tree with the real root and remove : any cruft that might be laying around. AFAIK this is the only way : to accomplish this. I thinks it's the only way currently implemented. One possible solution would be to keep a list in the relevant Makefiles of files to be removed when other things are installed. Once the bsd.* implementation is there, it should often be matter of moving things from one macro to another when something is removed. I don't think it's actually worth the effort to do right, so rather than doing it right, right now, I'll keep doing it the way you described above. -- Christopher Vance