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:subject:to:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ZtFkmaYDZ1iMtIEI
	8SjPw1qVurxcT1GZARnUR2S9k9kPgrS/VKmGfgvaWNNKejQb9TvJrTKlDW98MVOO
	Z2DgH8Gn5LDjP3JE9Yf5z9M65GACRVw9JynL5piEWdoz8bydOk14rCFq1yhDO1VJ
	kzFrqJUtS9X7ovlG025sUGvLN9U=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Jon Turney <jon.turney@dronecode.org.uk>
Subject: Re: [PATCH setup 0/3] Setup replacement for incver_ifdep
To: Achim Gratz <Stromeko-i47jiTeKxPI@public.gmane.org>, cygwin@cygwin.com
References: <1442937170-17580-1-git-send-email-jon.turney@dronecode.org.uk> <87mvwegy0r.fsf@Rainer.invalid>
Message-ID: <5602A5F4.3060505@dronecode.org.uk>
Date: Wed, 23 Sep 2015 14:15:32 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <87mvwegy0r.fsf@Rainer.invalid>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 22/09/2015 18:32, Achim Gratz wrote:
> Jon Turney writes:
>> Since we now have scripts which run on every setup run, a package which requires
>> another package to do some work after it is installed or uninstalled can create
>> a file to act as a trigger for that to happen.
>
> There aren't any stratified scripts for pre-remove, so a lot of the
> things that you might wish for don't work anyway.  So again it would
> need to be fixed without getting a trigger or setup would need to be
> made a lot smarter than it is today.

I thought that permanent postinstall scripts run even when no packages 
are being installed, or only packages are being removed, so they they 
are effectively run every time setup is?

>> Unfortunately, it's not very practical to change to doing that for the all
>> packages which contain info files, so I am suggesting this approach.
>
> So just do it unconditionally; I was planning to change _update-info-dir
> accordingly, but haven't found the time yet.  I do the same with mandb
> locally already and I haven't looked back.

Tempting, but I don't believe that is a good solution, since it adds the 
time it takes to rebuild the info directory to every setup run.

> $ time /etc/postinstall/update-info-dir.sh.done
>
> real    0m18.169s
> user    0m3.261s
> sys     0m5.703s

I also don't think it sets a good example.  Any other packages which 
require update scripts to run (which may take even longer) when packages 
are installed/removed, should not be doing that every time setup is run, 
if avoidable.

--
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