From: "Sam Edge (Cygwin)" <sam.edge.cygwin@gmx.com>
To: cygwin@cygwin.com
Subject: Re: Dependency issues in setup.ini.
Date: Sat, 30 Sep 2017 08:43:00 -0000 [thread overview]
Message-ID: <64ef1bd6-8db5-f540-a922-ea4d69822b06@gmx.com> (raw)
In-Reply-To: <59cecb88.c1d4ca0a.53569.24bf@mx.google.com>
On 29/09/2017 23:39, Steven Penny wrote:
> On Fri, 29 Sep 2017 21:16:17, "Sam Edge (Cygwin)" wrote:
>> 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!
>
> It is the job of the package manager to detect and avoid such loops.
> No database
> is perfect - it is up to the good programmer to account for an deal
> with problem
> data
>
>
Thanks for the clarification. Okay. Once I've written some code to
unpick which packages are erroneously creating the loops I'll report back.
Next question - :-) - should I report here or in cygwin-apps?
At the risk of getting a SHTDI response, perhaps part of the release
process for setup.ini should include a topological sort on '@
package'/'requires: package ...' pairs to flag up such issues? :-D
--
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
next prev parent reply other threads:[~2017-09-30 7:57 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) [this message]
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
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=64ef1bd6-8db5-f540-a922-ea4d69822b06@gmx.com \
--to=sam.edge.cygwin@gmx.com \
--cc=cygwin@cygwin.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).