delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/08/11/00:13:19

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 11 Aug 2008 00:12:25 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: setup v2.573.2.3: Postinstall: "abnormal exit: exit code=126"
Message-ID: <20080811041224.GA12423@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <00be01c8fa36$aaa16120$9601a8c0 AT CAM DOT ARTIMI DOT COM> <489DF631 DOT 57D5D4D6 AT dessent DOT net> <00db01c8fa5f$79ddb830$9601a8c0 AT CAM DOT ARTIMI DOT COM> <489E0C62 DOT 86E9115A AT dessent DOT net> <489E3393 DOT 4040300 AT byu DOT net> <489E4332 DOT 3060700 AT go4more DOT de> <489EEB8A DOT 7060408 AT byu DOT net> <489F64A5 DOT 3080309 AT users DOT sourceforge DOT net> <20080810231105 DOT GC9970 AT ednor DOT casa DOT cgf DOT cx> <489F93E7 DOT 4020108 AT cwilson DOT fastmail DOT fm>
MIME-Version: 1.0
In-Reply-To: <489F93E7.4020108@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sun, Aug 10, 2008 at 09:20:39PM -0400, Charles Wilson wrote:
> Christopher Faylor wrote:
>>> Actually, I was debating removing this from cygport and letting
>>> _update-info-dir take care of these, as this would appear to
>>> significantly reduce the number of postinstall scripts.
>> I think it's a good idea to just let _update-info-dir take care of this.
>> It's going to run anyway so you end up just running install-info twice.
>
> Well, one of the problems with both cygport's current automatic handling of 
> info files, and the _update-info-dir metapackage, is that nobody ever runs 
> install-info --remove. And really, I don't see any way a metapackage like 
> _update-info-dir could ever do so -- How does it know what I *used* to have 
> installed, that now is installed no longer?  It can't parse my existing dir 
> file, can it?

_update-info-dir deletes the dir file before it creates it.  The only
way an obsolete .info file can be added is if it somehow was not removed
by setup.

cgf

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019