Re: Dependency issues in setup.ini.
- Date: Sat, 30 Sep 2017 12:00:08 +0300
- From: Andrey Repin <anrdaemon@xxxxxxxxx>
- Subject: Re: Dependency issues in setup.ini.
Greetings, Sam Edge (Cygwin)!
> 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.
I'm eager to see the fruits of your labor.
> 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!
Dependency upon itself is curious, but other than that, this is a normal
situation for a package manager. Some packages are split for easier
maintenance of each, but are interlocked in their typical usage pattern.
> 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'?
While this is "not good", this is also not particularly bad for packages in
base - this group is always installed.
> Is this a known issue or should I report in more detail?
Nonetheless, such issues are best kept highlighted, unless it is clearly
seen/documented as intended.
With best regards,
Saturday, September 30, 2017 11:54:56
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple