From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) by sourceware.org (Postfix) with ESMTPS id 1E9D1385DC0A for ; Sat, 31 Oct 2020 19:27:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1E9D1385DC0A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([24.64.172.44]) by shaw.ca with ESMTP id YwXakk08SRAWfYwXbkfVDQ; Sat, 31 Oct 2020 13:27:55 -0600 X-Authority-Analysis: v=2.4 cv=P9aEOgMu c=1 sm=1 tr=0 ts=5f9dbabc a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 From: Brian Inglis Subject: Re: mingw64 packages Reply-To: cygwin-apps@cygwin.com To: cygwin-apps@cygwin.com References: <878sbmhhfp.fsf@Rainer.invalid> Autocrypt: addr=Brian.Inglis@SystematicSw.ab.ca; prefer-encrypt=mutual; keydata= mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0 LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5 /lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5 RSyTY8X+AQ== Organization: Systematic Software Message-ID: Date: Sat, 31 Oct 2020 13:27:54 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: <878sbmhhfp.fsf@Rainer.invalid> Content-Type: text/plain; charset=utf-8 Content-Language: en-CA Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfMXdrgv31HlpzW1dKdLcZZI3dnOMtchIc6Ym0sxCnOHlX9s524EjOlXTZS4QIU36kUoE+0e63TxnKACcen85KklaRY57S//mwWaFTSimzUk+rIzLIzoi JzmzM9MVVUWMwG4DhGegORJX9o5WShtGSUXziQ0JNXrmf9CRpi3gNMhGAYiGTd7ltUxMXp+Wn12wS50hbPzfJmQVpF8Hsctbof8= X-Spam-Status: No, score=-6.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Oct 2020 19:27:57 -0000 On 2020-10-31 03:29, Achim Gratz wrote: > Since I seem to pick up more of these… it is silly enough that you have > to have two almost identical cygport files for the two architectures, > but it does not make any sense to me to require these to be standalone > git repositories. They share the sources and (most) patches with the > Cygwin package of the same name and I don't really intend to track those > changes manually across multiple submodules. So I'd like to keep these > the same way I have done ZStandard: the Cygwin package and both MingW64 > packages in one Git repository. The different git upstreams are the only reasons we have to keep separate subdirectories for and copies of each of the mingw64-{x86_64,i686}-PKG files. > That of course doesn't work in the CI as Scallywag gets its knickers in > a twist when it sees more than one cygport file in the checkout. That > looks like something that could hopefully be solved with either a YAML > file or some more smarts on the Scallywag side? We could use one PKG-mingw.cygport and vary the inheritance and packages using a shell variable e.g. $ MINGW_ARCH=... cygport ... so the CI would always fail until it got smart enough! ;^> -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]