From: Andrey Repin <anrdaemon@yandex.ru>
To: Sam Edge <sam.edge@gmx.com>, cygwin@cygwin.com
Subject: Re: Dependency issues in setup.ini.
Date: Sat, 30 Sep 2017 11:51:00 -0000 [thread overview]
Message-ID: <19010162357.20170930142314@yandex.ru> (raw)
In-Reply-To: <171d601b-59c2-f186-5213-12c6b6f493cd@gmx.com>
Greetings, Sam Edge!
>>> 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.
> Ah, okay. Fair enough. It can be difficult to keep things layered purely
> up & down I know.
More than that, naive assumption of no circular dependency is the most common
cause for infinite recursions.
> Although often it can be resolved by introducing a
> third module that acts as the muxer between the other two to avoid cross
> API dependencies. But that's a discussion for another mailing list.
> But I'm also seeing loops deeper that X->Y->X. More like X->Y->Z->W->X.
A list indexed by package name is necessary when you resolve package
dependencies. Then you always know when to avoid dependency rescans.
> (The self-dependency is cygwin-debuginfo by the way.)
:)
>>> 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.
> Indeed. However, while off label usage of Cygwin is anathema to me but
> sometimes I wish 'base' wasn't quite so big and have to pare things down
> a little once installed, e.g. as part of a makefile- and/or
> Eclipse-based build tree in source code control.(Which was also one of
> my motivations for the Python stuff.)
Rational suggestions are always welcome, I suppose.
While my own usage of Cygwin is prone to spread thin across all aspects of my
daily work, I can see situations, where a much smaller subset of packages
(let's name it "core" or something) would be beneficial. I.e. when packaging
Cygwin as part of your own application.
--
With best regards,
Andrey Repin
Saturday, September 30, 2017 14:16:20
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2017-09-30 11:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 22:39 Sam Edge (Cygwin)
2017-09-29 23:54 ` Steven Penny
2017-09-30 8:43 ` Sam Edge (Cygwin)
2017-09-30 9:05 ` Marco Atzeri
2017-09-30 2:34 ` Doug Henderson
2017-09-30 7:57 ` Steven Penny
2017-09-30 10:57 ` Andrey Repin
2017-09-30 11:35 ` Sam Edge
2017-09-30 11:51 ` Andrey Repin [this message]
2017-09-30 13:28 ` Sam Edge
2017-10-02 13:25 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19010162357.20170930142314@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=sam.edge@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).