From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Shouldn't 'man' depend on 'col'? Shouldn't 'col' be easier to find?
Date: Wed, 09 Jul 2014 00:16:00 -0000 [thread overview]
Message-ID: <53BC89E9.2040303@cygwin.com> (raw)
In-Reply-To: <1737600071.20140708190126@breisch.org>
On 2014-07-08 18:01, Chris J. Breisch wrote:
> At Tuesday, July 8, 2014, 12:15:22 PM, Marco Atzeri wrote:
>> On 08/07/2014 17:47, Jack Duthen wrote:
>>> Question #3
>>> To get a 'man' that works when piped, is there a better way than
>>> loading this "random" collection of utilities?
>>>
>>> Am I the only one to get that problem???
>
>> util-linux is a popular package, so the issue was not yet noticed.
>
>> man was recently changed, so this dependency was likely missed,
>> specially as it seems hidden inside the man binary.
>
> Yes, this is true. I'll add it. I'm collecting a few things together,
Careful: right now util-linux requires: perl, so people will complain if
it gets pulled as is. I'll attempt to address this soon.
> and trying to get the DB creation to work a little faster as well.
That would be good, but there are some additional issues which make me
think we should drop this from postinstall.
Yaakov
--
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
next prev parent reply other threads:[~2014-07-09 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 15:47 Jack Duthen
2014-07-08 16:15 ` Marco Atzeri
2014-07-08 23:01 ` Chris J. Breisch
2014-07-09 0:16 ` Yaakov Selkowitz [this message]
2014-07-09 0:30 ` Chris J. Breisch
2014-07-09 22:28 ` Keith Christian
2014-07-10 6:21 ` Yaakov Selkowitz
2014-07-11 7:30 ` Erwin Waterlander
2014-07-11 9:35 ` Andrey Repin
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=53BC89E9.2040303@cygwin.com \
--to=yselkowitz@cygwin.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).