From owner-freebsd-stable Fri Nov 10 14:14:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id B0BDE37B479 for ; Fri, 10 Nov 2000 14:14:09 -0800 (PST) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA73075; Fri, 10 Nov 2000 17:14:08 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Fri, 10 Nov 2000 17:14:08 -0500 (EST) From: "Brandon D. Valentine" To: Brian Martinez Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ports question In-Reply-To: <3A0C6FB3.A3200428@no.spam.wanted.pilot.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Nov 2000, Brian Martinez wrote: >I'm just curious to know what people do about ports when there's an >update for the port (of after CVSup'ing the ports tree). For example, >if you have the apache_1.3.9-modssl port installed, what do you do when >you see the apache_1.3.14-modssl-latest-build port is released? Unless the new version has some security fix, bug fix, or new feature that I need, I generally leave well enough alone. >Generally I remove the 'work' directory, followed by a 'make deinstall' >and remove the files out of /usr/ports/distfiles. But it seems like >there would be an easier way. In the Apache case, I would need to make >a backup of my $apachedir/htdocs before the 'make deinstall' if I were >serving important information. Sometimes a backup could be huge, >depending on what someone is serving. make distclean will accomplish all of the file removal. Then a pkg_delete gets rid of the installed binaries. Do another make install from the ports directory and it will be replaced. Files in your htdocs, etc should not be removed by pkg_delete since they're not in the packing list. >What do people do on live/production systems? One fella said he does it >on 'updates' on a test system, then duplicates the filesystem over to >the live/production one. What if a test system is not available? Is >something like a 'make upgrade' feasible? In all honesty, I'm not >having any huge issues with this, it's just been on my mind lately, and >today my curiousity peaked :) If this is case I would do the following: cd make distclean make pkg_delete make install -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message