X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Sat, 3 Dec 2011 02:13:58 -0500 Message-ID: Subject: libneon27 requires libproxy1 which requires libglib2.0_0 From: Matthew Smith To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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. 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. -- 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