From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Add a command to make a test release
Date: Thu, 05 Oct 2017 12:24:00 -0000 [thread overview]
Message-ID: <b70a2040-102e-05f2-ac57-f2a454905f4d@dronecode.org.uk> (raw)
In-Reply-To: <blq7tc19ancq2idhesids18pu9odmnjg5h@4ax.com>
On 03/10/2017 21:01, Andrew Schulman wrote:
>> This patch (originally by Achim Gratz) adds a mechanism for generating
>> packages marked as 'test' as described in [1].
>>
>> I'm not committed to any of the details, but I would like to get
>> something with this functionality in, so tell me how you'd like it
>> implemented and I'll do it...
>>
>> [1] https://cygwin.com/ml/cygwin-apps/2016-12/msg00005.html
>
> Cygport needs a way to specify which versions are prev, curr, and test in
> cygport files. David Rothenberger and I each proposed a method [1,2]. It
> doesn't matter much to me which method is picked, but it's definitely a
> missing feature.
I'm not keen on the idea of including this transient information into
the cygport, and thus baking it into the source package.
However, I also want to make package maintainers lives easier. So, I'm
all for automation to make things less tedious and error-prone, which
this patch attempts to do.
A few points to consider:
* I'm going to remove the restriction that you can only have 3 versions.
(I keep on putting this off only because it will break parsing setup.ini
for setup prior to 2.877)
* (This also means that more than one test: version may be available)
* Changing curr: doesn't cause setup to downgrade (since 2.864) (unless
--force-current is used, since 2.874)
* prev: isn't a very significant label, since the only way to install
that version is by manually selecting it, i.e. all it means is "keep
this version around"
Taking a step back, as a package maintainer, what do you need to
control? What features do we need here?
next prev parent reply other threads:[~2017-10-05 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 19:51 Jon Turney
2017-10-03 20:01 ` Andrew Schulman
2017-10-03 20:25 ` Achim Gratz
2017-10-05 12:24 ` Jon Turney [this message]
2017-10-05 14:23 ` Andrew Schulman
2017-10-05 16:57 ` Ken Brown
2017-10-05 19:50 ` Andrew Schulman
2017-10-07 7:52 ` Achim Gratz
2017-10-09 19:33 ` Andrew Schulman
2017-10-05 18:16 ` Achim Gratz
2017-10-05 19:33 ` cyg Simple
2017-10-05 18:14 ` Achim Gratz
2017-11-01 19:58 ` 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=b70a2040-102e-05f2-ac57-f2a454905f4d@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).