DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=lMgfC
	4zqmFXaYRfsFFF9aIBqG7NcffduSdrLIaTgtgcP7SfV5WXf4wguPaMwF1ZSdsRWS
	hl0UbbOpTMy7AklwD72hU58iXC8MFuMUxyTBaxCDK87I6zrkY4S1vGeoLVByUlMX
	pnmXz7jtFC2PxgBXrV6eYlDxeBBPyJ7grmOaog=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Setup 2.774 texlive postinstall takes 10+ hours
References: <1414708038168-112334.post@n5.nabble.com>	<54567198.8000504@cornell.edu>	<20141103102515.GS14051@calimero.vinschen.de>	<87a948kvpw.fsf@Rainer.invalid>	<20141104085958.GA4932@calimero.vinschen.de>	<54618F4C.6000107@cygwin.com> <546191B0.4050808@cygwin.com>	<20141111115343.GQ2782@calimero.vinschen.de>	<546219A9.2070103@cornell.edu> <54622517.7030302@cornell.edu>	<20141111160239.GS2782@calimero.vinschen.de>
Date: Tue, 11 Nov 2014 18:08:35 +0100
In-Reply-To: <20141111160239.GS2782@calimero.vinschen.de> (Corinna Vinschen's	message of "Tue, 11 Nov 2014 17:02:39 +0100")
Message-ID: <87ppctu0ks.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Corinna Vinschen writes:
> On Nov 11 10:02, Ken Brown wrote:
>> Of course, this still doesn't solve the problem of making sure that the
>> _autorebase postinstall script runs whenever the user installs a package
>> containing DLLs.  I wonder if we should reconsider Achim's proposal.  If I
>> understand correctly, it is something like this (oversimplified):
>> 
>> 1. Change autorebase.bat to do an incremental rebase instead of trying to do
>> a full rebase.
>> 
>> 2. Arrange for autorebase.bat to never be marked as "done".
>> 
>> Achim, please correct me if my oversimplification distorts your suggestion
>> too much.
>
> Achim, can you give a management summary how your proposal works?

As Ken already correctly summarized, the autorebase postinstall script
will never be marked as done by setup.exe, so it will be run on each
install or update.  The incremental part ensures that this step doesn't
take too much time if there's nothing to do.  Currently this is based on
the name of that script, but it could be done differently.  The other
part is that all "perpetual" postinstall scripts are run before any
normal postinstall scripts, so these can assume to run in a correctly
rebased environment.

A slightly modified variant of the same mechanism could be used for
those infodir, icon cache and fontconfig updates, which should probably
be run after the normal postinstall scripts.  I think I've sent Ken a
sketch doing this from within a postinstall script for the texlive
packages, but providing some support from setup.ini and setup.exe for
stratified postinstalls (pre-post and post-post :-) would make this much
more robust.  I haven't yet coded up anything in that direction, though.

If you're wondering what happens when you've just installed a fresh
Cygwin: the perpetual rebase postinstall scripts detects the situation
and bails out, while the normal postinstall script does the initial
rebase (and is marked "done").  Which means we have to fix the
dependency problem anyway.

Incremental autorebase packages and patched setup.exe available on
request.


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

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple