Rafael Garcia-Suarez wrote:
It's probably related to Term::ReadLine::Gnu (which is not part of the
perl core.) I don't know much about your setup, but this is the module
which is linked against libreadline. Maybe the SuSE packages miss some
dependencies, or something.
-------
I don't really have Term-readline-gnu installed [yet].
===============================================================
A. Pagaltzis wrote:
>Hi Linda,
>
>do you need help maintaining Term::ReadLine::Gnu? :-)
>
-----------
Well not really, I really don't need it -- I was only
attempting to install it as a debugging aid for the error messages
I was getting when CPAN was starting up that involved valid lines
in my ~/.inputrc file (used by bash, as well).
lines like:
set expand-tilda on
set mark-symlinked-directories on
These used to be ignored by applications using readline for which they
apparently made no sense. I don't think it is a SuSE problem, since
it worked with their build of Perl-5.8.6. It's my "port" of 5.8.7
that seems to have raised this problem and am not entirely sure how or
why. Building Perl doesn't seem to be nearly so trivial or foolproof as
building the linux kernel, for example. So I'm sorta trying to
figure out why my perl build is complaining about bash-compatible
entries in .inputrc. While this might remotely be a CPAN thing,
it's beginning to appear more likely as something I did wrong in
my port/build of 5.8.7, though I attempted to use nearly the exact
same specfile as SuSE's 5.8.6, with it applying only the 1 patch file
for their default config setup. Any dependency faults are likely to
be my fault, not SuSE's....
Maybe this is only an issue for the perl5-porters list? Not too sure
about anything at this point.
Linda
