If I install another perl, do I try to get 'make configure-deps' to skip the perlsys/perl stage (if so how?), or is the idea that this bug might go away with an alternative perl?
I did a bit of googling and this bug seems to have been an issue with perl under SUSE v11. It has disappeared on my laptop (running openSUSE v12) but my system manager has elected to run suse enterprise which, while more stable, tends to be behind the times and is lissted as v11. I can commit the patch from my laptop, but would like to be able to install the fixed version on the system here so that others can access the fixed version of pamela, so I still want to get past this problem if possible.
|