Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 30 Oct 2000 12:22:41 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: "'cygwin AT sources DOT redhat DOT com'" <cygwin AT sources DOT redhat DOT com>
Subject: Re: Cygwin 1.1: setup of info files is incomplete.
Message-ID: <20001030122241.P2193@redhat.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: "'cygwin AT sources DOT redhat DOT com'" <cygwin AT sources DOT redhat DOT com>
References: <C322F78942E6D311AF8800D0B73C4FD8830DA4 AT CUPEX3 DOT rational DOT com> <20001030090039 DOT D1019 AT dothill DOT 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 AT sourceware DOT cygnus DOT com