public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Add a command to make a test release
Date: Thu, 05 Oct 2017 18:14:00 -0000	[thread overview]
Message-ID: <877ew9o42b.fsf@Rainer.invalid> (raw)
In-Reply-To: <b70a2040-102e-05f2-ac57-f2a454905f4d@dronecode.org.uk> (Jon	Turney's message of "Thu, 5 Oct 2017 13:24:51 +0100")

Jon Turney writes:
> I'm not keen on the idea of including this transient information into
> the cygport, and thus baking it into the source package.

Fair enough.  If that's the only thing that bothers you, this
information could easily live in some extra file that doesn't get
packaged.  Deal?

> 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.

I plan to modify the patch for test versions so that it automatically
produces one if the release starts with "0".  Thoughts?

> * 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)

HOw about for after we roll in libsolv and move to setup-3.x?

> * (This also means that more than one test: version may be available)

That seems awkward to handle.

> * Changing curr: doesn't cause setup to downgrade (since 2.864)
> (unless --force-current is used, since 2.874)

We need to eventually solve that problem in a different way, I think.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

  parent reply	other threads:[~2017-10-05 18:14 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
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 [this message]
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=877ew9o42b.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).