From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: missing perl directories
Date: Fri, 22 Jan 2021 17:36:17 +0100 [thread overview]
Message-ID: <715211bd-ed66-2537-9817-fe17eb6934d5@gmail.com> (raw)
In-Reply-To: <7e502f36-d045-4dc1-b9f1-dec329bca9f4@www.fastmail.com>
On 22.01.2021 17:15, Anthony Heading wrote:
> 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
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
>> no package should touch them
>
> Marco, I have no idea how to interpret that statement constructively.
Sorry, I should have be more clear.
We can discuss if the perl package should deliver empty directories like
usr/share/perl5/site_perl/
and similar. It seems reasonable but I am not a Perl expert, however
a distribution package should never write on "/usr/local"
https://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/usr.html
" The /usr/local hierarchy is for use by the system administrator when
installing software locally. It needs to be safe from being overwritten
when the system software is updated"
Regards
Marco
next prev parent reply other threads:[~2021-01-22 16:36 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 [this message]
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=715211bd-ed66-2537-9817-fe17eb6934d5@gmail.com \
--to=marco.atzeri@gmail.com \
--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).