Updated perl - broke stuff

[Paul Schmehl]

----- Original Message ----- 
From: "Ean Kingston" <ean at hedron.org>
To: <freebsd-questions at freebsd.org>
Cc: "Paul Schmehl" <pauls at utdallas.edu>
Sent: Sunday, February 13, 2005 3:42 PM
Subject: Re: Updated perl - broke stuff
>
> I stopped using portupgrade because it only upgrades ports that are out-of
> date. It then modifies the installed software database to change any
> dependencies that relied on the old port to show them as relying on the 
> new
> port.
>
> For most ports, this works. For Perl, particularly mod_perl, this doesn't
> work. If you install a new perl you have to rebuild everything that 
> depends
> on perl even if it hasn't been updated.
>
> So I stopped using portupgrade.
>
Wouldn't it make more sense to fix mod_perl?  (Or portupgrade - whichever 
one is the culprit?)  All the ports that depended upon perl appear to have 
had their dependencies updated properly except for libwww and mod_perl. 
ISTM, fixing those two ports makes more sense.

If you don't use portupgrade, then what *do* you do?  Wouldn't you have to 
deinstall and reinstall every port that depended upon perl?  Or will 
pkgdb -F do the trick?

Paul Schmehl (pauls at utdallas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/