From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH setup] Finish providing support for provides: and conflicts:
Date: Wed, 06 Jun 2018 20:44:00 -0000 [thread overview]
Message-ID: <a6938431-ea1f-2ecd-c885-cd824e554ced@dronecode.org.uk> (raw)
In-Reply-To: <dac0ef15-a58f-a2e4-9b32-1b66c68c43c1@cornell.edu>
On 04/04/2018 14:21, Ken Brown wrote:
> On 3/21/2018 3:38 PM, Ken Brown wrote:
>> Introduce member functions SolvableVersion::provides() and
>> SolvableVersion::conflicts(). This enables packagedb::read() to
>> access provides and conflicts lists from setup.ini.
>
> Ignore this patch. It breaks libsolv's dependency processing.
>
Thanks, even if it's not right, I'd completely overlooked the need for
something like this.
next prev parent reply other threads:[~2018-06-06 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 19:38 Ken Brown
2018-04-04 13:21 ` Ken Brown
2018-06-06 20:44 ` Jon Turney [this message]
[not found] ` <6fb8aceb-7a04-36e8-c14f-4d182bd27e1e@dronecode.org.uk>
2018-06-18 17:49 ` Ken Brown
2018-06-19 12:43 ` Ken Brown
2018-06-23 15:10 ` Ken Brown
2018-07-06 16:28 ` Jon Turney
2018-07-06 22:19 ` Ken Brown
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=a6938431-ea1f-2ecd-c885-cd824e554ced@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).