From: "Anthony Heading" <anthony@ajrh.net>
To: cygwin@cygwin.com
Subject: Re: missing perl directories
Date: Fri, 22 Jan 2021 16:15:29 +0000 [thread overview]
Message-ID: <7e502f36-d045-4dc1-b9f1-dec329bca9f4@www.fastmail.com> (raw)
In-Reply-To: <d56b5b94-febf-bd4d-ead1-200b900e89a4@SystematicSw.ab.ca>
Hi Brian!
On Fri, Jan 22, 2021, at 7:33 AM, Brian Inglis wrote:
> either something has not completed correctly, or something is missing in recent
> installations.
I think that's right. Those the directories which are referenced in the binary, I know the generic upstream perl source process has always created them, but they're not included in the current cygwin package. As a total guess, empty directories are maybe now being elided in the cygwin packaging process?
% strings - /bin/cygperl5_30.dll | grep /usr/local
/usr/local/lib/perl5/site_perl/5.30/x86_64-cygwin-threads
/usr/local/share/perl5/site_perl/5.30
% cygcheck -p site_perl
Found 4 matches for site_perl
grepmail-5.3033-2 - grepmail: search mailboxes for mail matching an expression (installed binaries and support files)
perl-Stow-2.3.1-1 - perl-Stow: perl library for stow
perl-Stow-2.3.1-2 - perl-Stow: Perl library for stow
perl-Stow-2.3.1-3 - perl-Stow: Perl library for stow
On Thu, Jan 21, 2021, at 4:22 PM, Marco Atzeri via Cygwin wrote:
> /usr/local/* are "local"
>
> no package should touch them
Marco, I have no idea how to interpret that statement constructively.
next prev parent reply other threads:[~2021-01-22 16:17 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 [this message]
2021-01-22 16:36 ` Marco Atzeri
2021-01-22 17:53 ` Anthony Heading
2021-01-22 19:43 ` Ken Brown
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=7e502f36-d045-4dc1-b9f1-dec329bca9f4@www.fastmail.com \
--to=anthony@ajrh.net \
--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).