From: Richard Beels <rbeels@yahoo.com>
To: cygwin@cygwin.com
Subject: Re: Package Requests: Update: bash-completion, coreutils - New: linux-manpages
Date: Fri, 13 Aug 2021 16:48:47 -0400 [thread overview]
Message-ID: <20210813204847.Olap7vOTvlYhVHvu6oeGQBlcjuF70HKit1is8Yd5suA@z> (raw)
In-Reply-To: <3f699992-7099-a677-be65-4efd143ac587@SystematicSw.ab.ca>
At 8/13/2021 at 01:11, Shakespearean monkeys danced on Brian Inglis's
keyboard and said:
> I suggested linux-manpages a while back, as it comes from the same
> source as posix-manpages, and I install it myself, but did not get
> voted to package, due to duplication with conflicting priorities
> and no easy way to resolve under existing paths.
Huh... they go to /usr/local by default (easily changeable with
`make prefix=...`), which is pretty bare to begin with and with the
fact that they don't package hardly anything in man1, the conflict
potential goes down even further. Ah well, I guess I just keep
making it manually from a cloned repo.
> I could probably look at bash-completion if I can get around to
> bash, as I would worry about dependencies, fixes, and tweaks. There
> are big challenges in bash and coreutils being years out of date as
> parts of those need customized for Cygwin, and the customization
> patches are likely to have issues, or even need redesign, if there
> have been major changes.
bash-completion is a separate/disconnected project (now located at
https://github.com/scop/bash-completion), it doesn't align its
releases with bash itself. bash-completion 2.7-2.10 require bash
4.1+, 2.11 bumped that to 4.2. Since we're at 4.4, I don't think
that's a showstopper (BICBW).
And thanks again for the findutils update. 4.7 gave us
comma-delimited -type/-xtype specs, so a "( -type p -o -type s )"
(shown non-quoted for sanity's sake) becomes "-type p,s". :thumbsup:
next prev parent reply other threads:[~2021-08-13 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210813042232.5DB54397102F@sourceware.org>
2021-08-13 5:11 ` Brian Inglis
2021-08-13 20:48 ` Richard Beels [this message]
2021-08-13 20:48 ` Richard Beels
2021-08-13 20:48 ` Richard Beels
[not found] ` <20210813204955.88404386184A@sourceware.org>
2021-08-14 3:19 ` Brian Inglis
2021-08-13 4:20 Package Requests: Update:bash-completion, " Richard Beels
-- strict thread matches above, loose matches on Subject: below --
2021-08-13 4:20 Richard Beels
2021-08-13 4:20 Richard Beels
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=20210813204847.Olap7vOTvlYhVHvu6oeGQBlcjuF70HKit1is8Yd5suA@z \
--to=rbeels@yahoo.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).