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:

% 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).

Similar to your reference to the FHS,  the corresponding Perl policy intends 
that "site_perl" is to be used by the local SA.  There is a "vendor_perl" 
concept instead to support this kind of cygwin packaging, as you can see 
referenced in the default path above.

But the Stow example is a distraction which compounds two problems, so let's 
leave that aside.

At core, this is catch 22.
  -  The perl build reserves, creates, and expects to exist,  an empty 
directory for the sole use of the SA:   "site_perl".   
  -  Cygwin perl assigns that directory location into the tree similarly 
intended for the SA:   "/usr/local"
  -  Your strict interpretation of the FHS disallows the empty site_perl 
directory to be created for use by the SA because it's positioned within a tree 
reserved for use by the SA

I dunno,  Marco,  I'm not so dogmatic, and I can fix my own installation.  I 
just thought this would be a helpful bug report for others.   It sounds like we 
can find enough conflicting Cygwin policy documents to ensure that there is no 
solution,  so that's delightful.





--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

Reply via email to