From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128]
Date: Thu, 30 May 2013 10:27:00 -0000 [thread overview]
Message-ID: <20130530090831.GK4471@calimero.vinschen.de> (raw)
In-Reply-To: <51A6948B.3000807@users.sourceforge.net>
On May 29 18:51, Yaakov (Cygwin/X) wrote:
> But now that you mention it, is cygutils *supposed* to be in Base?
> It is marked category: Utils, but seems to be pulled into Base only
> because of cygwin-doc (which *is* in Base, oddly enough; shouldn't
> it just be Doc?) listing it as a dependency.
That sounds strange. Was cygwin-doc always in Base? It contains the
cygwin docs and basic man pages but that doesn't really qualify for the
Base category.
Also, why does cygwin-doc depend on cygutils at all? It only contains
info and man pages, so the deps should be coreutils and man, but nothing
else, AFAICS.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
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:[~2013-05-30 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 16:04 cygutils Postinstall Script Errors With Exit Code 128 Reini Urban
2013-05-29 19:50 ` Paul.Nickerson
2013-05-29 23:51 ` Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128] Charles Wilson
2013-05-30 0:43 ` Yaakov (Cygwin/X)
2013-05-30 10:27 ` Corinna Vinschen [this message]
2013-05-30 21:26 ` Charles Wilson
2013-05-31 8:51 ` Corinna Vinschen
2013-06-05 16:47 ` Yaakov (Cygwin/X)
2013-06-06 15:17 ` Charles Wilson
2013-05-30 20:50 ` Charles Wilson
2014-07-16 1:54 ` cygutils Postinstall Script Errors With Exit Code 128 dylanhay
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=20130530090831.GK4471@calimero.vinschen.de \
--to=corinna-cygwin@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).