In response to Harlan Stenn <[EMAIL PROTECTED]>: > 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?
I'm not familiar with using "make update" and I don't see any info on it in man ports. However, the procedure I described will manipulate your package database. It does not change anything in the ports tree itself. As a result, tools (such a portupgrade) that use the package database to determine dependencies will continue to use that data. It is possible that future, drastic reorganizations to the ports tree could force you to do additional manual corrections, but it's been my experience that you'll have that now and again no matter what you do. -- Bill Moran Collaborative Fusion Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
