From: Sam <email_sam@posteo.de>
To: Marc Chantreux <eiro@phear.org>
Cc: help-guix@gnu.org
Subject: Re: ripit/perl: use perl_cddb_get package?
Date: Sat, 09 Nov 2019 11:47:57 +0100 [thread overview]
Message-ID: <23036934e4ef38c0592d485903f82838@posteo.de> (raw)
In-Reply-To: <20191109091152.GA18779@prometheus.u-strasbg.fr>
Hey marc, thanks for answering.
> perl -E 'map say, grep -d, @INC'
>
> should provide a direcory that contains CDDB_get.pm
This seems to be the problem, it returned:
$ perl -E 'map say, grep -d, @INC'
/gnu/store/ziinjmbnq004866mwjrczsk12wf35qb8-perl-5.30.0/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi
/gnu/store/ziinjmbnq004866mwjrczsk12wf35qb8-perl-5.30.0/lib/perl5/site_perl/5.30.0
/gnu/store/ziinjmbnq004866mwjrczsk12wf35qb8-perl-5.30.0/lib/perl5/5.30.0/x86_64-linux-thread-multi
/gnu/store/ziinjmbnq004866mwjrczsk12wf35qb8-perl-5.30.0/lib/perl5/5.30.0
But
$ find /gnu/store/*perl* -iname "CDDB_get.pm"
/gnu/store/7n8rdqbx25801ypj38bywacbicmsc2ns-perl-cddb-get-2.28/lib/perl5/site_perl/5.28.0/CDDB_get.pm
/gnu/store/mg8qgzi0v2his2xld1zkb8x7p5lf3v6m-perl-cddb-get-2.28/lib/perl5/site_perl/5.30.0/CDDB_get.pm
I then copied the perl script and manually pointed to the dir (use lib
'/gnu/store/mg8qgzi0v2his2xld1zkb8x7p5lf3v6m-perl-cddb-get-2.28/lib/perl5/site_perl/5.30.0/';)
and the error got replaced by a different one, but with the same cause
(this time it was about "LWP::Simple", I tried the same trick, but
apparently this module is not part of perl-http-daemon).
So it seems like the problem is that this perl script package can't see
the installed perl modules?
I am unsure if this is a bug, thinking about opening an issue because at
least without cddb_get, the package won't work.
Any input is appreciated.
Thanks,
Sam
next prev parent reply other threads:[~2019-11-09 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 1:31 ripit/perl: use perl_cddb_get package? Sam
2019-11-09 9:11 ` Marc Chantreux
2019-11-09 10:47 ` Sam [this message]
2019-11-09 11:24 ` Marc Chantreux
2019-12-18 14:22 ` Sam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23036934e4ef38c0592d485903f82838@posteo.de \
--to=email_sam@posteo.de \
--cc=eiro@phear.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).