In Options.pm: use IO::Wrap qw/wraphandle/; use IO::Scalar; Those 2 Perl modules are not included in dev-lang/perl-5.18.2-r1 and also are not available in Portage.
How does it fail? It looks to compile ok for me
When I try to download epgdata: Can't locate IO/Wrap.pm in @INC (you may need to install the IO::Wrap module) (@INC contains: /etc/perl /usr/local/lib64/perl5/5.20.2/x86_64-linux /usr/local/lib64/perl5/5.20.2 /usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux /usr/lib64/perl5/vendor_perl/5.20.2 /usr/local/lib64/perl5 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/5.20.2/x86_64-linux /usr/lib64/perl5/5.20.2 .) at /usr/lib64/perl5/vendor_perl/5.20.2/XMLTV/Options.pm line 38. BEGIN failed--compilation aborted at /usr/lib64/perl5/vendor_perl/5.20.2/XMLTV/Options.pm line 38. Compilation failed in require at /home/thomas/tv_grab_eu_epgdata.pl line 148. So, it seems the epgdata script needs Options.pm and Options.pm needs IO/Wrap.pm.
(In reply to thomas from comment #0) > In Options.pm: > use IO::Wrap qw/wraphandle/; > use IO::Scalar; > > Those 2 Perl modules are not included in dev-lang/perl-5.18.2-r1 and also > are not available in Portage. You're missing a dependency on dev-perl/IO-stringy (In future similar cases, * check if module is included in core perl by "corelist -a IO::Wrap" * search for the module on http://search.cpan.org/ )
It looks like xmltv-0.5.57 requires IO::Wrap unconditionally, but the requirement is only on some of its use flags (the offending line in XMLTV/Options.pm is not in the newest version, which is the first ebuild I wrote). I'll see if I can get the dependency added to the 0.5.57, but in the meantime you can work around this by either emerging dev-perl/IO-stringy, or adding a USE flag to xmltv for one of the backends that does pull it in (e.g. uk_rt).
Created attachment 429482 [details] build.log xmltv-0.5.67 fails to buid with "Can't locate Term/ReadKey.pm in @INC". This may or may not also be an issue with 0.5.57.
I have added the missing IO-Stringy dependency in 0.5.70. TermReadKey was already added to 0.5.68. I'll leave it to the maintainer to stabilise and clean up.
should be fixed now. closing