From: Ricardo Wurmus <rekado@elephly.net>
To: Chris Keschnat <chris@catsu.it>
Cc: help-guix@gnu.org
Subject: Re: Correct way to install perl-anyevent-i3?
Date: Wed, 27 Jul 2022 16:25:47 +0200 [thread overview]
Message-ID: <878roer5r1.fsf@elephly.net> (raw)
In-Reply-To: <867d3yis8u.fsf@catsu.it>
Chris Keschnat via <help-guix@gnu.org> writes:
> So I added =perl-anyevent-i3= to the package definition (in the =operating-system=).
> After a =guix system reconfigure= and a reboot, =i3-save-tree= is still giving the same error.
>
> There seems to be something wrong with the load path
> (I don't know perl terminology, but I hope it is clear what I mean).
You’ll need to add this to the Perl load path, which is controlled with
the PERL5LIB environment variable. When Perl is installed in the same
profile this variable will be set automatically.
--
Ricardo
next prev parent reply other threads:[~2022-07-27 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 13:28 Correct way to install perl-anyevent-i3? Chris Keschnat via
2022-07-27 14:25 ` Csepp
2022-07-27 14:25 ` Ricardo Wurmus [this message]
2022-07-27 17:28 ` Chris Keschnat via
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=878roer5r1.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=chris@catsu.it \
--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).