From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: libneon27 requires libproxy1 which requires libglib2.0_0
Date: Mon, 05 Dec 2011 02:20:00 -0000 [thread overview]
Message-ID: <1323051626.6872.9.camel@YAAKOV04> (raw)
In-Reply-To: <CAGHSphZsRm7DxB-TPsHPTborUBQOMbqmJjYLjW5pxENDxj-ymg@mail.gmail.com>
On Sat, 2011-12-03 at 02:13 -0500, Matthew Smith wrote:
> After running setup.exe to add a package I noticed something had decided
> to pull in some gnome libraries. As best I can tell its due to libneon27
> requiring libproxy1 though I may be missing something else. I did manage
> to find this regarding libproxy.
The latest libneon27 does require libproxy1-0.4.7, which pulls in only
libglib2.0_0, and I wouldn't count that as "some gnome libraries".
> From http://cygwin.com/ml/cygwin/2010-05/msg00605.html
> >libproxy pulls in these packages as dependencies for its GNOME and KDE
> >integration modules. libproxy was added as a libsoup-gnome dependency,
> >for which these deps are anyways required. But if neon is going to use
> >libproxy as well, these modules are not strictly required, so I removed
> >their deps from libproxy0/setup.hint (and from the upcoming libproxy1
> >as well).
>
> So hopefully nothing else has changed and it's easy to fix.
I'm not sure what your question is here. There's nothing here to "fix".
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:[~2011-12-05 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 7:14 Matthew Smith
2011-12-05 2:20 ` Yaakov (Cygwin/X) [this message]
2011-12-07 13:40 ` Matthew Smith
2011-12-07 23:24 ` Yaakov (Cygwin/X)
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=1323051626.6872.9.camel@YAAKOV04 \
--to=yselkowitz@users.sourceforge.net \
--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).