Date: Sat, 20 Jan 2001 13:16:35 -0600 (CST) From: Mike Meyer <mwm@mired.org> To: "Shawn Barnhart" <swb@grasslake.net> Cc: questions@freebsd.org Subject: Re: Trashed /var, fixing /var/db/pkg Message-ID: <14953.58387.710254.822185@guru.mired.org> In-Reply-To: <47169656@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Shawn Barnhart <swb@grasslake.net> types: > 1) Using /usr/ports/distfiles as a guide, copy the matching entries from > another 4.2-STABLE box of near identical vintage. Some minor risk of > variation, but both boxes were built within days of each other and I don't > think the ports I've installed are terribly in terms of their rate of > change. This ensures that I'm not actually overwriting any existing ports. > > 2) Using the distfiles as a guide, go through and remake and reinstall each > port. This should rebuild /var/db/pkg entries with 100% accuracy, but I'm > also worred that it will trash or overwrite existing config files. > > Which is the best option? > > (1) Seems the fastest although it has the slight risk that some port I've > installed differs in file content or layout and may overwrite my existing > config. > > (2) Seems the most accurate, although it'd be big drag to rebuild the ports > right just to get my config files clobbered on reinstall. As a general rule > do port builds respect existing config files, or do they just clobber them? As a general rule, ports don't install config files, but install samples. However, that's just a rule. You can check pkg-plist in each port (or pkg/PLIST if your ports structure is old) to see if what they create. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14953.58387.710254.822185>