Am 20.07.2011 04:45, schrieb Doug Barton:
On 07/19/2011 17:04, jsb...@speakeasy.net wrote:
Apologies for two subjects.
Don't apologize, just don't do it. :)
Disheartened by the perl 5.12.3 5.12.4 bump; I've figured how to upgrade
(for some reason perl-after-upgrade does little on these
on 20/07/2011 03:04 jsb...@speakeasy.net said the following:
for some reason perl-after-upgrade does little on these machines
Just in case - have you read its man page and have you ever try to run
perl-after-upgrade -f ?
--
Andriy Gapon
___
Quoth Andriy Gapon on Wednesday, 20 July 2011:
on 20/07/2011 03:04 jsb...@speakeasy.net said the following:
for some reason perl-after-upgrade does little on these machines
Just in case - have you read its man page and have you ever try to run
perl-after-upgrade -f ?
Well, that explains
Apologies for two subjects.
1...
After rebuilding ports recently, a ldd recursing of usr/local/bin discovers a
whole slew of ports which should have also had their versions minor bumped.
Most of those, libgcrypt.so ... although maybe fewer than those found in
actuality, though maybe not.
On 07/19/2011 17:04, jsb...@speakeasy.net wrote:
Apologies for two subjects.
Don't apologize, just don't do it. :)
Disheartened by the perl 5.12.3 5.12.4 bump; I've figured how to upgrade
(for some reason perl-after-upgrade does little on these machines), but
the time to do so seems
