Upgrading perl modules (as ports) and "already installed" problems

Tillman Hodgson tillman at seekingfire.com
Mon Nov 17 07:14:33 PST 2003


I'm looking for the appropriate portupgrade magic to handle these sorts
of situations automatically:

      You may wish to ``make deinstall'' and install this port again
      by ``make reinstall'' to upgrade it properly.
      If you really wish to overwrite the old port of www/p5-HTML-Tagset
      without deleting it first, set the variable "FORCE_PKG_REGISTER"
      in your environment or the "make install" command line.

This happens when upgrade perl modules ports a /lot/ for me. As I use
HTML::Mason on my production web sites, this makes a Perl upgrade a
lengthy and error-prone manual operation.

As an example of what I currently do, take the upgrade to perl 5.8.2.
After portupgrading it, apache will not restart as mod_perl is in the
5.8.1 dir. Thus I'd do a `portupgrade -f mod_perl` and it will do it's
thing until it encounters a sub-port that gives the above error message.
Then I'd do a `cd <port_dir> && make deinstall && make reinstall &&
portupgrade -f mod_perl`. Repeat for the next perl module.

Whats the best way to ensure that all perl modules are properly and
automatically upgrade when perl itself is upgraded?


There is no history of mankind, there are only many histories of all
kinds of aspects of human life. And one of these is the history of
political power. This is elevated into the history of the world.
	- Karl Popper, _The Open Society and its Enemies_

More information about the freebsd-questions mailing list