Date: Sun, 13 Feb 2005 16:02:06 -0600 From: "Paul Schmehl" <pauls@utdallas.edu> To: <freebsd-questions@freebsd.org> Subject: Re: Updated perl - broke stuff Message-ID: <04e901c51217$c3d5e590$7702a8c0@officeeagle> References: <200501271852.j0RIqQ9t010411@mp.cs.niu.edu><44is5imspz.fsf@be-well.ilk.org> <04d201c51214$4bb07ab0$7702a8c0@officeeagle> <200502131642.59595.ean@hedron.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Ean Kingston" <ean@hedron.org> To: <freebsd-questions@freebsd.org> Cc: "Paul Schmehl" <pauls@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@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/~pauls/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04e901c51217$c3d5e590$7702a8c0>