From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) by sourceware.org (Postfix) with ESMTPS id 0B1D8385828E for ; Fri, 17 Feb 2023 21:42:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0B1D8385828E Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=Shaw.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=shaw.ca Received: from shw-obgw-4002a.ext.cloudfilter.net ([10.228.9.250]) by cmsmtp with ESMTP id T5F0pQbMLuZMST8UypeNlR; Fri, 17 Feb 2023 21:42:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=shaw.ca; s=s20180605; t=1676670152; bh=vATvkSM9HRi2tNIelleN9w183VIo9O4ZQzr2zU9Z9Sc=; h=Date:Reply-To:Subject:To:References:From:In-Reply-To; b=ry1B1RaTKbdj3/9JsUHARC+SR1vxHumgW5At4Ax1Jb1Zj3GIU+p/ekHLGxfx23XlA 9GUjhE7xHdHxvJSmQbF2DhNLdiHyZqN4GLlUhzmbimTQqfh6J9DVvHYTqwB3XarVba VAcWGb+Chi8WILawess5ZKl5AUlDQqLmiX+owSVPWyNpJIRHP41FF08iKrK6EycNHS BQ/9b9lpbCHCOLsJTnpDOOtXAc8ZQ3/z49nzM4r8bcvHN3jdtNugo/sUMM4XWCrWqJ kgrm1YUCkJ/BpcbeJmAGxbDvlYMRNYNXK0HMjUJhw1lrnnxWTPxIWxfdf7rfp6TOhL 3gCt0IXOASHIA== Received: from [10.0.0.5] ([184.64.102.149]) by cmsmtp with ESMTP id T8UxpDegByAOeT8UyphUwU; Fri, 17 Feb 2023 21:42:32 +0000 X-Authority-Analysis: v=2.4 cv=e5oV9Il/ c=1 sm=1 tr=0 ts=63eff4c8 a=DxHlV3/gbUaP7LOF0QAmaA==:117 a=DxHlV3/gbUaP7LOF0QAmaA==:17 a=IkcTkHD0fZMA:10 a=SWObRRwmSiw9tjlUVBMA:9 a=QEXdDO2ut3YA:10 Message-ID: <297a2cbe-96f5-702d-0c7a-e785ff3c421b@Shaw.ca> Date: Fri, 17 Feb 2023 14:42:31 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Reply-To: cygwin-apps@cygwin.com Subject: Re: Possible "stage" token for SCALLYWAG builds Content-Language: en-CA To: cygwin-apps@cygwin.com References: <131eb6f8-0b9d-ed93-a986-e556808865ee@cornell.edu> From: Brian Inglis Organization: Inglis In-Reply-To: <131eb6f8-0b9d-ed93-a986-e556808865ee@cornell.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfLK2NU+M8n4lQmRq9r7MABLRbxoncBTOGSMPfzY5pcITXyL0K61XKFUx1p9iyGkdJj9sicFf+S3eIX6mlJoAKfOdtaFw3YOziBVlRrx1ZCW8CzEZg1m5 6A2zYPZgMSwJwakeLbIcgxAC1OU5h6/otFM4HtgWN/5W/cnHGcATX5o27CkaKMPONPyqLU8+C1v3Eg== X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2023-02-16 17:13, Ken Brown via Cygwin-apps wrote: > On 2/16/2023 3:31 PM, Jon Turney wrote: >> On 15/02/2023 21:48, Ken Brown via Cygwin-apps wrote: >>> When building TeX Live (once a year), I have to build texlive, asymptote, and >>> all the texlive-collection-* packages.  I currently can't use SCALLYWAG to do >>> the builds because these packages need to all be deployed at once.  So I have >>> to build them all locally, upload them to my staging area, and then upload >>> !ready files, one for x86_64 and one for noarch. >>> >>> It would be convenient for me if SCALLYWAG would accept a "stage" token that >>> would upload the files to my staging area without deploying them. Then I >>> could let SCALLYWAG do the builds, and I could upload the !ready files when >>> everything is staged. >>> >>> If I'm the only maintainer who would find this useful, then I can continue >>> doing it the way I always have.  But maybe others would find it useful too. >> >> I'm not opposed to adding a some feature to support this if needed, but from >> the way you are describing it, this sounds more like a constraint that the >> dependency solver should be aware of. >> >> (just because texlive-2023 and texlive-collection-foo-2023 are made available >> to download at the same time, doesn't mean that they always end up installed >> together, as the user might alter the version of one or the other) >> >> If they really must be kept in lockstep to work correctly, then there's at >> least a couple of ways of doing that: >> >> * give texlive an additional provide, such as texlive_2023, and make >> everything that requires it, require that (something similar is done with perl >> and perl modules) >> >> * make things which require texlive do so with a version constraint like >> 'requires: texlive (>= 20230000), texlive (<20240000)' (in theory this works, >> but I have no doubt that a bug will emerge when someone tries to use it, and >> ofc, it relies on the range of future versions which are compatible being >> correctly known in advance) > > Thanks for the suggestions.  I think I should be able to make things work with > one or both of your ideas. Would make sense if scallywag could stage as well as deploy, perhaps using a cygport all-stage command similar to all-test, perhaps when time permits? Could also deploy in test SCALLYWAG="deploy", then untest each when you want to deploy. -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry