Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 7 Jun 2003 00:39:03 +0100
From:      =?iso-8859-1?Q?Marco_Gon=E7alves?= <info@kolorbit.com>
To:        <freebsd-isp@freebsd.org>, "Lewis Watson" <lists@visionsix.com>
Subject:   Re: Updating Ports on Production Servers
Message-ID:  <00b001c32c84$d4135d90$a51216c3@celeron1700>
References:  <00f501c32c82$c53e9750$de0a0a0a@vsis169>

next in thread | previous in thread | raw e-mail | index | archive | help
you really should check out portupgrade tool
http://www.freshports.org/sysutils/portupgrade/


Bet regards
Marco Gonçalves

----- Original Message ----- 
From: "Lewis Watson" <lists@visionsix.com>
To: <freebsd-isp@freebsd.org>
Sent: Saturday, June 07, 2003 12:24 AM
Subject: Updating Ports on Production Servers


> I am a big fan of the ports collection and use the ports to build the
> programs I use on our production servers. Now I am wanting to update some
> ports and have a chicken and egg issue. If I go ahead and update a port
> (pure-ftpd for example)...
>
> After I run "CVSUP portfile"  the old version that's running has no
> graceful way of being removed.  If I try to remove it I am notified that
> the version that is running is not on the machine so then I guess force
> the uninstall? Either that or just do a make - make install and overwrite
> the old port binaries with the new binaries ( this does not seem good
> either).
>
> It appears the only way to cleanly upgrade a port is to deinstall the
> current port. Run CVSUP portfile... and get the new port files... do a
> make - make install and get the new version of the port installed. This
> opens the machine to several minutes of downtime while the program is
> being made... (not good either)
>
> Please tell me the way that it's being handled on your servers/ network...
> Thanks!
> Lewis
>
>
> _______________________________________________
> freebsd-isp@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
>
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00b001c32c84$d4135d90$a51216c3>