From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 616 invoked by alias); 6 Feb 2016 15:31:13 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 597 invoked by uid 89); 6 Feb 2016 15:31:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=H*F:D*org.uk, orphaned, UD:info, Hx-spam-relays-external:ESMTPA X-HELO: out4-smtp.messagingengine.com Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sat, 06 Feb 2016 15:31:09 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A75C320775 for ; Sat, 6 Feb 2016 10:31:06 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Sat, 06 Feb 2016 10:31:06 -0500 Received: from [192.168.1.102] (host86-141-131-217.range86-141.btcentralplus.com [86.141.131.217]) by mail.messagingengine.com (Postfix) with ESMTPA id 4357E68013A; Sat, 6 Feb 2016 10:31:06 -0500 (EST) Subject: Re: [PATCH setup 0/3] Setup replacement for incver_ifdep To: cygwin-apps@cygwin.com, Ken Brown References: <87lhb8htrh.fsf@Rainer.invalid> <561FA783.900@dronecode.org.uk> <87oag0qad3.fsf@Rainer.invalid> <20151019154100.GB18989@calimero.vinschen.de> <87io62hiz6.fsf@Rainer.invalid> <20151020102150.GF5319@calimero.vinschen.de> <56532D34.4090102@dronecode.org.uk> <87bnakmtqc.fsf@Rainer.invalid> <56549774.2090008@dronecode.org.uk> <87ziy3utip.fsf@Rainer.invalid> <20151126101120.GA6674@calimero.vinschen.de> <56AA50E4.2040105@dronecode.org.uk> <56AA6128.8030700@cornell.edu> <56AA74BE.4010208@redhat.com> <56AA7755.8060801@cornell.edu> <56AA787A.9080503@redhat.com> <56AB75A4.6060101@dronecode.org.uk> <56AB7CD7.5000101@cornell.edu> <56B6033C.3050407@cornell.edu> From: Jon Turney Message-ID: <56B611AE.7050404@dronecode.org.uk> Date: Sat, 06 Feb 2016 15:31:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <56B6033C.3050407@cornell.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-02/txt/msg00002.txt.bz2 On 06/02/2016 14:29, Ken Brown wrote: > On 1/29/2016 9:53 AM, Ken Brown wrote: >> On 1/29/2016 9:22 AM, Jon Turney wrote: >>> On 28/01/2016 20:22, Eric Blake wrote: >>>> On 01/28/2016 01:17 PM, Ken Brown wrote: >>>>> Second, why is the second line needed, i.e., under what circumstances >>>>> would it be expected to succeed after the first install-info command >>>>> failed? >>>> >>>> Sadly, I don't know install-info enough to answer that one. >>> >>> I think the first install-info command would fail if the .info file is >>> missing a START-INFO-DIR-ENTRY/END-INFO-DIR-ENTRY block, in which case >>> install-info should fail with a 'install-info: warning: no info dir >>> entry in `xxx.info'' >>> >>> Since such a .info file is apparently valid (although I don't think we >>> have any instances of such), I guess the nonsense after the || should be >>> fixed to use '$f' correctly. >> >> I have a few instances of those files on my system: >> >> install-info: warning: no info dir entry in >> `/usr/share/info/automake-history.info.gz' >> install-info: warning: no info dir entry in >> `/usr/share/info/automake-history1.12.info.gz' >> install-info: warning: no info dir entry in >> `/usr/share/info/automake-history1.13.info.gz' >> install-info: warning: no info dir entry in >> `/usr/share/info/texdraw.info.gz' >> >> But I'm not convinced that we need to worry about them. It could be >> that they're intended to be cited from other info files but not to be >> listed in the top level directory. I would say that if an info file >> lacks a START-INFO-DIR-ENTRY/END-INFO-DIR-ENTRY block, we should assume >> that its author didn't want it listed in the directory. > > Jon, any further thoughts about this? texinfo-6.1 has just been > released, so I can go ahead with adding the postinstall script as soon > as we decide what it should do in the case of a missing > START-INFO-DIR-ENTRY/END-INFO-DIR-ENTRY block. I think you are right, so just drop the || and everything after it. (As an aside, I don't think it's necessarily correct that those nodes you list are orphaned, e.g. automake-history1.12.info should be referred to in automake1.12.info, but in fact that has references to automake-history.info)