Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 30 Oct 2000 12:22:41 -0500 From: Christopher Faylor To: "'cygwin@sources.redhat.com'" Subject: Re: Cygwin 1.1: setup of info files is incomplete. Message-ID: <20001030122241.P2193@redhat.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: "'cygwin@sources.redhat.com'" References: <20001030090039.D1019@dothill.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20001030090039.D1019@dothill.com>; from Jason.Tishler@dothill.com on Mon, Oct 30, 2000 at 09:00:39AM -0500 On Mon, Oct 30, 2000 at 09:00:39AM -0500, Jason Tishler wrote: >On Fri, Oct 27, 2000 at 02:00:10PM -0700, Masterson, Dave wrote: >> The 'info' command (from Texinfo) looks for "dir" (directory) files to >> determine what the menu is that should be displayed when invoked. This file >> is not created by the installation of Cygwin 1.1. However, the nature of >> this "dir file is such that it needs to be updated (pretty much) after every >> package installation -- it really can't be included in any particular >> package. Could "setup" be adjusted to run "install-info" after every >> package installation? > >I agree with the above, but I think that it should be generalized. >There are postinstall tasks that should be one-shot (i.e., as currently >implemented in setup) and ones that should be executed every time (e.g., >regenerating the info dir files). The question is how to best integrate >the support of both one-shot and every time postinstall scripts into DJ's >setup? That's one question. The more important question is "Who's going to do the work?" cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com