Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Thu, 15 Nov 2001 20:01:31 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: nano - packaged and ready for some criticism :) Message-ID: <20011116010131.GA13068@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <06a501c16e2a$18a71750$0200a8c0 AT lifelesswks> <3BF4523C DOT 7020801 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BF4523C.7020801@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Thu, Nov 15, 2001 at 06:39:40PM -0500, Charles Wilson wrote: >Robert Collins wrote: > > >>3) I'd suggest ( cd /usr/info ; for i in nano.info ; do install-info >>$i --dir-file=dir ; done ) instead of installing _every_ info file in >>the directory, as that could get quite slow :]. > > >I'll take the blame for this. Two of my recent packages (the experimental >versions of autoconf and automake wrapper scripts) had postinstall scripts >that installed *every* info file. This was a thinko on my part, but it >seems to have spread... Is it really that slow to do this? You actually end up with some benefit since the dir file could be fixed "automatically" if it was screwed up before. cgf