public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: package cygwin-d-... case sensitivity problems --
Date: Thu, 20 Jun 2019 03:18:00 -0000	[thread overview]
Message-ID: <0398e13d-1f13-fed2-4d33-34a84d706b3d@SystematicSw.ab.ca> (raw)
In-Reply-To: <90b5e010-fbcd-aebf-a88a-fc8c40134575@SystematicSw.ab.ca>

On 2019-06-19 20:45, Brian Inglis wrote:
> 
> On 2019-06-18 11:46, Townsend, Paul wrote:
>> The cygwin-doc-... package has several problems in at least the 
>> /usr/share/man/man3 directory where multiple file names differ only in case, 
>> i.e., the tar file contains, in this order,
>>   usr/share/man/man3/jN.3.gz
>>   usr/share/man/man3/jn.3.gz
>> The jN.3.gz file contains the roff text and the jn.3.gz file contains a roff 
>> .so directive pointing at jN.3.  The file that ends up in man3 is jn.3.gz
>> and jN.3.gz disappears.
>> The simplest solution would be to just remove jn.3.gz and similar .so files 
>> from the tarball.  This would at least allow the roff text files to exist.
>> FMI - where was the tarball created?  It certainly was not on a computer
>> with Windows and case insensitivity.
> 
> A lot of package maintainers work on Linux and test in Windows VMs.
> These conflicts should be picked up by the setup program tar extract.

As most if not all of the math library and docs are part of and shared with
newlib, most of the maintenance will be done in Linux, where these .so refs are
necessary.

The Cygwin doc packaging will have to patch this to avoid using the other cased
variants of any man pages which are symlinks or only contain .so refs: the only
file currently matching those criteria is jn.3.gz.

Anyone can fix this locally by extracting the newlib doc from your Cygwin
mirror's downloaded tar case sensitively to your Cygwin root as:
$ /bin/tar -xvf
...mirror/x86_64/release/cygwin/cygwin-doc/cygwin-doc-3.0.7-1.tar.xz
usr/share/man/man3/jN.3.gz -C /

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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

      reply	other threads:[~2019-06-20  3:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 17:46 Townsend, Paul
2019-06-20  0:51 ` Townsend, Paul
2019-06-20  2:46 ` Brian Inglis
2019-06-20  3:18   ` Brian Inglis [this message]

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=0398e13d-1f13-fed2-4d33-34a84d706b3d@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).