Date: Tue, 6 May 2003 22:59:39 -0400 (EDT)
From: Garrett Wollman <wollman@lcs.mit.edu>
To: Garance A Drosihn <drosih@rpi.edu>
Cc: current@freebsd.org
Subject: Re: hardcoded -C argument to ${INSTALL}
Message-ID: <200305070259.h472xdam068443@khavrinen.lcs.mit.edu>
In-Reply-To: <p0521060bbade23ef6ad5@[128.113.24.47]>
References: <3EB8109D.2060307@isi.edu> <20030507083913.Y18014@gamplex.bde.org> <p0521060abaddf1caa9fc@[128.113.24.47]> <200305070126.h471QjNr067902@khavrinen.lcs.mit.edu> <p0521060bbade23ef6ad5@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Tue, 6 May 2003 22:53:10 -0400, Garance A Drosihn <drosih@rpi.edu> said: > Do the mtree files reflect options the administrator has set when > doing a buildworld, things like NO_KERBEROS or NO_PERL or NO_GAMES, > etc, etc? Not currently, but that can be arranged. (Just build a release with your favorite options set.) Of course, you lose the benefit of being able to piggyback someone else's effort that way, but them's the breaks. Each installation `dist' has its own mtree file. Where this really helps is in figuring out what your starting point is: 99% of all FreeBSD installations were created from released installation media at some point in the murky past. So, if you're updating a 4.7 system to -current, you can easily identify which of the files you have *came with* that installation, and follow the removal of files through 4.8, 5.0, and soon 5.1. We release often enough that this is sufficient for most people's purposes. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305070259.h472xdam068443>