DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=kPsgrShJZ1dh/8u5
	TvV/JyE+bFHpPJqKv1FTFh8jeVXmR/Q3baDMjDID2HYLsLegriO0efz2JGfcX6+v
	etxLJQ5sAzsWw9H0ySuZcfNoCa6umqwKbejov7fXyibQsfAZ+irOqLTnZyRtVrmE
	si29lw2exFV3HPYHCjiNQhKEhHM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: setup graphical chooser : how to list orphaned packages ?
To: cygwin@cygwin.com
References: <f506efbf-e1b1-db71-ebda-47509227aa88@wanadoo.fr> <2d3c5da1-5944-ef91-aa48-faed2210b772@cornell.edu> <f36bc02e-ca7a-3065-b789-f57d44abe453@laposte.net> <1bc4a9a6-c543-e78b-62fe-2e7ac696a1df@cornell.edu> <58894cff-9ff6-9297-9efb-d37db9e49804@wanadoo.fr> <f03576c5-41b3-26c8-db27-06d9f885cb3a@cornell.edu> <2b33c8ad-9cf3-cff5-fc44-8a5c82709006@laposte.net> <87wp3yhma5.fsf@Rainer.invalid> <cc85243b-e5f8-20e6-4306-e4e69ae50707@SystematicSw.ab.ca> <b267d6c4-fcae-31b0-df4f-20d797e37a86@cornell.edu> <a7757470-e946-4b63-fcc2-fac47404da32@gmail.com> <1833fa94-bd81-d2f0-ea4c-b5d2ac43cd3b@gmail.com> <2578ae0a-a6ed-9a12-502b-5d584cf194a1@gmail.com>
From: Ken Brown <kbrown@cornell.edu>
Message-ID: <82d84cc5-a51c-08cb-73e1-14c8d149528d@cornell.edu>
Date: Sun, 15 Oct 2017 12:10:37 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <2578ae0a-a6ed-9a12-502b-5d584cf194a1@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 10/15/2017 12:24 AM, cyg Simple wrote:
> On 10/14/2017 12:11 PM, Marco Atzeri wrote:
>> On 14/10/2017 17:31, cyg Simple wrote:
>>
>>>>
>>>> This is very common.  Suppose you have package A installed, which
>>>> requires B.  Package B gets obsoleted by C.  But A still requires B
>>>> until someone (usually the maintainer of A) changes this to make A
>>>> require C instead.
>>>>
>>>
>>> Maybe a column showing what installed packages are depending on B and a
>>> column showing the dependencies for package A would be nice?  It would
>>> help clear the confusion anyway.
>>
>>
>> the cygcheck-dep package can provide dependencies information,
>> I do not see the need for setup to do it
>>
> 
> So the information is available just in a different place than where it
> should be, the tool I'm using to do the download.  Having a separate
> package to tell me the package dependencies isn't very friendly; I might
> not have anything installed, certainly not cygcheck-dep and then I have
> to learn and remember to use it as a side step of installation.

I think most users would be distracted by seeing the dependencies 
displayed and would have no need for this information.  On the rare 
occasions when they are surprised that something got installed, they can 
use cygcheck-dep (or ask on the list) to find the reason.

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