Date: Tue, 25 Apr 2006 22:11:44 +0200 From: hans@lambermont.dyndns.org (Hans Lambermont) To: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> Cc: freebsd-ports@freebsd.org Subject: Re: libtool upgrade, entry 20060223 in UPDATING Message-ID: <20060425201144.GB4435@leia.lambermont.dyndns.org> In-Reply-To: <20060425214257.6648ca76@it.buh.tecnik93.com> References: <20060425154800.GB1351@leia.lambermont.dyndns.org> <444E4624.6070509@vonostingroup.com> <20060425182639.GC1351@leia.lambermont.dyndns.org> <20060425214257.6648ca76@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ion-Mihai Tetcu wrote: > Hans Lambermont wrote: >> Frank Laszlo wrote: >>> Hans Lambermont wrote: >>>> The 20060223 entry in UPDATING suggests that the only reliable way >>>> of upgrading a system is to remove all packages and reinstalling >>>> from scratch. >> ... >>>> Next to that I'd like to hear from others how to accomplish this >>>> all-ports upgrade on servers where one wants the downtime to be >>>> minimal. >>> >>> portupgrade -afp isnt good enough? >> >> No, I want to have minimal downtime of the server. When using >> 'portupgrade -afp' the system is in flux for almost a week. I want to >> avoid that, and the only way I know how to avoid that is to use a >> staging and build server (at least that's the idea). > > If you can build your ports on an non-production server, use > portugrade -PP with modified package site in pkgtools.conf Ah yes, that avoids using pkg_add and it's 200-packages-at-a-time limit. I'm also looking into other-than-portupgrade ports tree tools, does anyone know a way to accomplish the equivalent of portupgrade -PP ? > If you can afford that non-production server the fastest way is to > delete all installed packages and build them all from scratch. Which is exactly what I did :) Still took me almost a week. regards, -- Hans Lambermont
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060425201144.GB4435>