From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: How to override previous version?
Date: Sun, 11 Dec 2016 00:03:00 -0000 [thread overview]
Message-ID: <9f69c324-982a-de40-1b1a-f7ff0082a202@dronecode.org.uk> (raw)
In-Reply-To: <23d13e3b-760f-d911-4251-f79fee18caea@acm.org>
On 10/12/2016 22:42, David Rothenberger wrote:
> When I package Subversion, I usually leave the last major release as the
> previous version in setup because there are compatibility issues when
> updating major releases.
>
> I'm now a little confused about how to accomplish this with the new
> pvr.hint scheme. I think I just need to upload an override.hint file,
> but I'm not sure what its contents should be nor whether I need to make
> one for each package or just one for the entire directory.
>
> Subversion has many child packages, so I get a dist tree with the
> top-level subversion package and then subdirectories for each child
> package. Now each of these have a separate pvr.hint file.
>
> I'm trying to package 1.9.5-1 and 1.8.17-1. Would I do this by creating
> an override.hint file in the top-level dist directory with the contents:
>
> prev: 1.8.17-1
>
> Is that sufficient? Any advice would be appreciated.
That looks like the right contents.
But currently, an override.hint is required for each (sub)package.
prev parent reply other threads:[~2016-12-11 0:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 15:28 per-version hints proposal Jon Turney
2016-06-21 12:03 ` Corinna Vinschen
2016-06-21 13:49 ` Marco Atzeri
2016-06-21 14:28 ` Corinna Vinschen
2016-06-21 15:32 ` Marco Atzeri
2016-06-21 14:09 ` Eric Blake
2016-06-21 14:27 ` Corinna Vinschen
2016-06-21 18:04 ` Achim Gratz
2016-06-21 18:27 ` Jon Turney
2016-08-30 12:24 ` Jon Turney
2016-08-31 19:14 ` Achim Gratz
2016-09-01 17:15 ` Jon Turney
2016-12-08 19:30 ` Jon Turney
2016-12-09 10:46 ` Corinna Vinschen
2016-12-09 11:10 ` Corinna Vinschen
2016-12-12 13:29 ` Jon Turney
2016-12-12 13:29 ` Jon Turney
2017-04-08 17:00 ` Achim Gratz
2017-04-12 20:51 ` Ken Brown
2017-04-13 6:24 ` Achim Gratz
2016-09-17 6:15 ` Achim Gratz
2016-09-18 5:17 ` Marco Atzeri
2016-09-18 15:14 ` Jon Turney
2016-09-18 16:12 ` Achim Gratz
2016-09-18 16:29 ` Achim Gratz
2016-09-19 15:37 ` Ken Brown
2016-09-19 18:24 ` Achim Gratz
2016-09-19 22:23 ` Jon Turney
2016-09-18 16:40 ` Ken Brown
2016-09-18 16:53 ` Marco Atzeri
2016-09-18 17:16 ` Achim Gratz
2016-09-18 18:08 ` Marco Atzeri
2016-09-22 13:44 ` Eric Blake
2016-12-10 22:42 ` How to override previous version? David Rothenberger
2016-12-11 0:03 ` Jon Turney [this message]
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=9f69c324-982a-de40-1b1a-f7ff0082a202@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).