Date: Thu, 18 Oct 2007 18:18:51 -0400 From: Gerard <gerard@seibercom.net> To: User Questions <freebsd-questions@freebsd.org> Subject: Re: Updating Ports Message-ID: <20071018181326.9389.GERARD-SEIBERT@seibercom.net> In-Reply-To: <471786EC.3040803@mtmary.edu> References: <18199.32078.807531.40747@jerusalem.litteratus.org> <471786EC.3040803@mtmary.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On October 18, 2007 at 12:16PM Peter Clark wrote:
{ ... ]
> Now that I have reread what I wrote, it seems a bit unclear. I have not
> used either service before. Seeing as I am looking at using this in
> production server environment I would not look at frequently making
> changes as one might in a desktop application. I am looking for an
> elegant way to update ports when it is required to. Are there more
> concerns about one updater over the other? Maybe this is a moot point.
> If you installed a port with some additional config args can you either
> supply them the upgrade program or can it be reread from the previous
> install somehow? I really am just trying to find a relatively simple way
> to make sure that a port gets upgraded and that I do not lose any of it
> dependencies in the process.
I have used both without any major problems. I usually run portupgrade to do
normal port upgrading; however, every so often, I run 'portmanager -u -p -l'
which seems to catch a lot of discrepancies in the builds and corrects them.
Other than that, both programs seem to work quite well. If you use portmanager,
do use the '-l' switch to force a log file. It comes in handy if something
goes wrong.
--
Gerard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071018181326.9389.GERARD-SEIBERT>