From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: why gtk2.0-engines depends on libgtk2.0-devel ?
Date: Sun, 29 Oct 2017 21:30:00 -0000 [thread overview]
Message-ID: <90e8a1c6-d43f-6440-1de7-a2e8e19d00d9@cornell.edu> (raw)
In-Reply-To: <dc946135-15e1-1406-817f-537186940169@wanadoo.fr>
On 10/29/2017 1:28 PM, Jérôme Bouat wrote:
> Hello.
>
>> Fixed, thanks for the report.
>>
>
> When will this change be released ? I have a lot of dependencies which
> are pulled from this initial dependency.
It's already been released, in the sense that gtk2.0-engines no longer
depends on libgtk2.0-devel. But if you were hoping that the additional
dependencies would be automatically uninstalled, that won't happen. You
have to uninstall them manually (or just ignore them unless you're short
on disk space). cygcheck-dep can help you find them.
Ken
--
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
prev parent reply other threads:[~2017-10-29 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 19:57 Jérôme Bouat
2017-10-26 20:14 ` Yaakov Selkowitz
2017-10-29 17:28 ` Jérôme Bouat
2017-10-29 21:30 ` Ken Brown [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=90e8a1c6-d43f-6440-1de7-a2e8e19d00d9@cornell.edu \
--to=kbrown@cornell.edu \
--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).