From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 52409 invoked by alias); 5 Oct 2017 18:14:11 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 52397 invoked by uid 89); 5 Oct 2017 18:14:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=packaged, Hx-spam-relays-external:ESMTPA X-HELO: vsmx011.vodafonemail.xion.oxcs.net Received: from vsmx011.vodafonemail.xion.oxcs.net (HELO vsmx011.vodafonemail.xion.oxcs.net) (153.92.174.89) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 05 Oct 2017 18:14:09 +0000 Received: from vsmx003.vodafonemail.xion.oxcs.net (unknown [192.168.75.197]) by mta-5-out.mta.xion.oxcs.net (Postfix) with ESMTP id 78E0D3E866E for ; Thu, 5 Oct 2017 18:14:07 +0000 (UTC) Received: from Gertrud (p5b2f3642.dip0.t-ipconnect.de [91.47.54.66]) by mta-7-out.mta.xion.oxcs.net (Postfix) with ESMTPA id 4E0A1300D85 for ; Thu, 5 Oct 2017 18:14:05 +0000 (UTC) From: Achim Gratz To: cygwin-apps@cygwin.com Subject: Re: [PATCH cygport] Add a command to make a test release References: <0756319a-94e5-d3d3-507a-2aee9418aca6@dronecode.org.uk> Date: Thu, 05 Oct 2017 18:14:00 -0000 In-Reply-To: (Jon Turney's message of "Thu, 5 Oct 2017 13:24:51 +0100") Message-ID: <877ew9o42b.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-VADE-STATUS: LEGIT X-SW-Source: 2017-10/txt/msg00036.txt.bz2 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