Dependency issues in setup.ini.

["Sam Edge (Cygwin)" <sam.edge.cygwin@gmx.com>]

Hi all.

I've been developing a Python package that can interrogate and
manipulate local package caches (the directories where setupXXX.exe
keeps its downloads) and installation databases (from Cygwin
/etc/setup/installed.db files) with a mind to pruning, merging and
reporting in the spiript of Michael A. Chase's 'clean_setup' utility but
as a scriptable tool set rather than a stand-alone utility.

It's not production ready yet but it's already flagged up some issues.

For example we have lots of dependency loops in the 'requires' fields in
setup.ini - even to the point that some packages depend upon themselves!

And also we have some dependency omissions. For example, mintty doesn't
depend upon anything - it has no requires field. Surely, every binary
package should depend at least upon 'cygwin'?

Is this a known issue or should I report in more detail?

-- 
Sam Edge


--
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