From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH cygport] Generate a separate .hint for the source package
Date: Sat, 22 Feb 2020 14:48:00 -0000 [thread overview]
Message-ID: <20200222144751.22096-1-jon.turney@dronecode.org.uk> (raw)
In-Reply-To: <20200208134634.58200-1-jon.turney@dronecode.org.uk>
Incremental to the previous, since it uses the hint testing framework that
provides, this adds generation of a separate .hint for the source package.
(This is something I should have proposed a while ago, not least because it
simplifies how calm can determine if a .hint file is stale (which currently
has to use some complex logic to see if it's being used by a source or an
install package, which still doesn't always work correctly))
Jon Turney (1):
Generate a separate .hint for the source package
lib/pkg_pkg.cygpart | 21 ++++++++++++-------
.../dist/multiple/multiple-3.14-1-src.hint | 6 ++++++
testsuite/hints/multiple/multiple.cygport | 1 +
.../dist/single/single-2.3.4-1-src.hint | 5 +++++
4 files changed, 25 insertions(+), 8 deletions(-)
create mode 100644 testsuite/hints/multiple/hints/multiple-3.14-1.x86_64/dist/multiple/multiple-3.14-1-src.hint
create mode 100644 testsuite/hints/single/hints/single-2.3.4-1.x86_64/dist/single/single-2.3.4-1-src.hint
--
2.21.0
next prev parent reply other threads:[~2020-02-22 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 13:47 [PATCH cygport 0/2] Add provides: and conflicts: Jon Turney
2020-02-08 13:47 ` [PATCH cygport 2/2] Add provides: and conflicts: hints Jon Turney
2020-02-08 13:47 ` [PATCH cygport 1/2] Add test which compares hints with expected Jon Turney
2020-02-22 14:48 ` Jon Turney [this message]
2020-02-22 14:48 ` [PATCH cygport 3/2] Generate a separate .hint for the source package Jon Turney
2020-03-24 3:07 ` [PATCH cygport 0/2] Add provides: and conflicts: Yaakov Selkowitz
2020-04-05 14:17 ` Jon Turney
2020-04-06 23:11 ` Yaakov Selkowitz
2020-04-06 23:11 ` Yaakov Selkowitz
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=20200222144751.22096-1-jon.turney@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).