This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Is there a limitation I don't know about in setup.exe dependency checking?
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 08 Sep 2008 12:27:49 -0700
- Subject: Re: Is there a limitation I don't know about in setup.exe dependency checking?
- References: <025301c911d1$8b3f7a80$9601a8c0@CAM.ARTIMI.COM>
- Reply-to: cygwin-apps at cygwin dot com
Dave Korn wrote:
> want to trace the dependency? That is to say, is it not allowed/intended to
> satisfy a missing dependency with a "test" version?
I think it tries to satisfy the dependency with whatever the current
global trust level is set to. So if the radio button is on Curr but
there's no Curr version available, it won't do anything. But if the
radio button is Exp then it should be able to add in Exp versions. (I'd
have to dig into the code to see whether this is truly the case or
whether it's just hardcoded to Curr only. I think that's a bug if
true.)
Now admittedly this is really stupid logic. It should try to match the
trust level of whatever was just selected when adding dependent
packages.
Brian