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 <pkgname> 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 <portdir>
make distclean
make
pkg_delete <portname>
make install
--
Brandon D. Valentine <[EMAIL PROTECTED]>
"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 [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
