X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2C923386F414 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=nexgo.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=Stromeko AT nexgo DOT de From: Achim Gratz To: cygwin AT cygwin DOT com Subject: Re: postinstall: fontconfig abnormal exit References: <106370283 DOT 20200908171659 AT yandex DOT ru> <782011494 DOT 20200910083521 AT yandex DOT ru> <5a2fdf46-93c8-048b-cadb-cb9d9212c716 AT SystematicSw DOT ab DOT ca> <20200910230426 DOT 5811f3e8 AT quarternote> <8f40571c-1a37-8e4b-f1bd-ecf40175d0d7 AT gmail DOT com> <179bbaf0-02b4-1c63-0083-5fa2a8833ea9 AT cornell DOT edu> <06e9cf44-8cc8-267e-12b3-e8a866a01c80 AT gmail DOT com> Date: Fri, 11 Sep 2020 22:30:59 +0200 In-Reply-To: (Ken Brown via Cygwin's message of "Fri, 11 Sep 2020 15:47:14 -0400") Message-ID: <87h7s45a4c.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-VADE-STATUS: LEGIT X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, 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 AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Ken Brown via Cygwin writes: > Unfortunately, this doesn't yet fix the problem with > fontconfig_dtd.sh. The latter will now succeed if it is run after > libxml2.sh, but not if it is run first. I'm not aware of any way to > force setup to run one postinstall script before another. Multiple ways: 1. Make the libxml postinstall script sort lexically before any others that depend on it. Obviously this is brittle, but it might work in this particular instance (autorebase does this). 2. Make the libxml catalog creation a perpetual postinstall script with prefix "0p_". That only works if it doesn't depend on other postinstall scripts having their work completed. 3. Implement and use the stratified postinstall concept originally outlined at: https://sourceware.org/legacy-ml/cygwin-apps/2014-12/msg00148.html 4. Use the package dependency order to order the postinstall script activation. With libzypp we should have the correct information, we'd just need to somehow make the packagemeta iterator use it. That still won't work if we have dependency loops. 5. (Try to) Run any failed postinstalls again in setup and bail only if the number of fails does not decrease from the last iteration. At the time it was deemed too complicated and so we only use the "end" strata for the perpetual postinstall scripts. As said then, there would need to be some serious discussion on how to coordinate the strata assignments. 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple