Date: Mon, 13 Nov 2006 13:25:01 -0500 From: Harlan Stenn <Harlan.Stenn@pfcs.com> To: Bill Moran <wmoran@collaborativefusion.com> Cc: ports@freebsd.org, Harlan Stenn <Harlan.Stenn@pfcs.com> Subject: Re: portupgrade, apache2/apache22, php4/php5 Message-ID: <20061113182501.EE51B2841A@gwc.pfcs.com> In-Reply-To: <20061113125057.f8334988.wmoran@collaborativefusion.com> References: <20061113173025.E8A672841A@gwc.pfcs.com> <20061113125057.f8334988.wmoran@collaborativefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Bill, > Using portupgrade's -o option, you can replace on port with another. > For example: > portupgrade -o www/apache22 apache > > Will replace whatever version of apache you've got installed with > Apache-2.2, including rearranging any required dependencies so they > point to the new port. Usually, when I have problems with portupgrade > like you describe, it's because some already installed port requires > something I don't want as a dependency. The above trick has fixed it > every time for me. Will this "keep" across a "make update", or do I need to re-do it every time I update /usr/ports? H
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061113182501.EE51B2841A>