From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: missing perl directories
Date: Fri, 22 Jan 2021 14:43:43 -0500 [thread overview]
Message-ID: <b6accad3-a806-9da0-1ad3-41d8f89be453@cornell.edu> (raw)
In-Reply-To: <62b9ab58-2bed-4b7f-b16b-a89535e13cd5@www.fastmail.com>
On 1/22/2021 12:53 PM, Anthony Heading wrote:
> On Fri, Jan 22, 2021, at 4:36 PM, Marco Atzeri via Cygwin wrote:
>>
>> not on usr/local
>>
>> perl-Stow: Perl library for stow
>>
>> 2020-02-04 19:14 0 usr/share/perl5/
>> 2020-02-04 19:14 0 usr/share/perl5/site_perl/
>> 2020-02-04 19:14 0 usr/share/perl5/site_perl/5.30/
>> 2020-02-04 19:14 0 usr/share/perl5/site_perl/5.30/Stow/
>> 2020-02-04 19:14 5559
>> usr/share/perl5/site_perl/5.30/Stow/Util.pm
>> 2020-02-04 19:14 70081 usr/share/perl5/site_perl/5.30/Stow.pm
>>
>
> Correct. And of course that means this Stow package doesn't actually work:
Achim has already answered your original question, but I just want to chime in
to correct your misstatement.
> % perl -MStow -e ''
> Can't locate Stow.pm in @INC (you may need to install the Stow module) (@INC contains: /usr/local/lib/perl5/site_perl/5.30/x86_64-cygwin-threads /usr/local/share/perl5/site_perl/5.30 /usr/lib/perl5/vendor_perl/5.30/x86_64-cygwin-threads /usr/share/perl5/vendor_perl/5.30 /usr/lib/perl5/5.30/x86_64-cygwin-threads /usr/share/perl5/5.30)
perl-Stow works fine. It's intended to be used by /usr/bin/stow, which knows
where to find it.
Ken
next prev parent reply other threads:[~2021-01-22 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 16:09 Anthony Heading
2021-01-21 16:22 ` Marco Atzeri
2021-01-22 7:33 ` Brian Inglis
2021-01-22 16:15 ` Anthony Heading
2021-01-22 16:36 ` Marco Atzeri
2021-01-22 17:53 ` Anthony Heading
2021-01-22 19:43 ` Ken Brown [this message]
2021-01-22 20:29 ` Achim Gratz
2021-01-22 19:35 ` Achim Gratz
2021-01-22 21:05 ` Anthony Heading
2021-01-23 19:08 ` Achim Gratz
2021-01-24 16:14 ` Anthony Heading
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b6accad3-a806-9da0-1ad3-41d8f89be453@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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).