From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
"Schulman, Andrew" <schulman.andrew@epa.gov>
Subject: Re: replacing a previous package verson
Date: Mon, 11 Apr 2022 15:33:33 +0100 [thread overview]
Message-ID: <99e29d4f-220a-c9ac-448b-a13b95db0d00@dronecode.org.uk> (raw)
In-Reply-To: <f6c85hl6hthdg7mgkgfn3rj5j8078i8l4t@4ax.com>
On 11/04/2022 14:45, Andrew Schulman via Cygwin-apps wrote:
>> After all this time I feel that I should know the answer to this, but here
>> goes.
>>
>> I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
>> leaving fish-3.3.1-1 as the previous release.
>>
>> What's the best way to do this? Should I create override.hint, with
>>
>> keep: 3.3.1-1
>> replace-versions: 3.4.0-1
>>
>> ? This seems as though it might be right, but one question I have is, will
>> override.hint persist in future releases unless I replace it?
>
> Or, should I just set
>
> prev: 3.3.1-1
>
> in fish.cygport, and let cygport and calm handle it from there?
The explicit 'prev/test/curr: <version>' lines which could appear in
setup.hint aren't supported anymore (see [1]), since there are now
different, hopefully better and less ambiguous ways of conveying that
information.
[1] https://cygwin.com/pipermail/cygwin-apps/2020-March/039948.html
next prev parent reply other threads:[~2022-04-11 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 13:02 Andrew Schulman
2022-04-11 13:45 ` Andrew Schulman
2022-04-11 14:33 ` Jon Turney [this message]
2022-04-11 13:49 ` Jon Turney
2022-04-11 15:34 ` Andrew Schulman
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=99e29d4f-220a-c9ac-448b-a13b95db0d00@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=schulman.andrew@epa.gov \
/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).