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: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3BF597DD.C5979366@ece.gatech.edu>
Date: Fri, 16 Nov 2001 17:49:01 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin-apps AT cygwin DOT com
Subject: Re: nano - packaged and ready for some criticism :)
References: <OE14B5VROXacMj0AGUO000119f7 AT hotmail DOT com> <06a501c16e2a$18a71750$0200a8c0 AT lifelesswks> <3BF4523C DOT 7020801 AT ece DOT gatech DOT edu> <20011116010131 DOT GA13068 AT redhat DOT com> <3BF48060 DOT 7010406 AT ece DOT gatech DOT edu> <008c01c16e5f$684f4ae0$0200a8c0 AT lifelesswks> <20011116193923 DOT GM17035 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)

Christopher Faylor wrote:
> 
> On Fri, Nov 16, 2001 at 04:27:38PM +1100, Robert Collins wrote:
> >
> >===
> >> --> The info package should have this script -- either in
> >/usr/bin/fix-info
> >> or /etc/postinstall/info.sh (or both).
> >
> >Who is the info maintainer? Chris? Can said maintainer please put a
> >postinstall script to regen info.dir completely in the next release....
> 
> I guess I'm maintaining texinfo.
> 
> I can do this, sure.
> 
> I wonder if all of the packages correctly rely on info, though.

Good point.  If they install info files, then they need to call
install-info during the setup/install process -- which means they need
to depend on texinfo.  (I betcha my own packages don't follow this
rule....oops)
 
> And, this just causes info to regen the 'dir' file if it is installed,
> right?  It won't solve the problem of adding a new .info file.

You are correct.  If texinfo has an /etc/postinstall/info.sh script,
then it will regen the dir file when *texinfo* is reinstalled.  If
texinfo has a /usr/bin/fix-info script, then we can instruct new
(confused) users to run that script if/when their info stops working.

Neither solves the problem of what setup should do with a binary package
that contains info files.  Possibilities:

1) all maintainers must include a postinstall script that calls
install-info for each of their own info files.

2) setup magic:
    (in C++) for each fn in (`tar tvjf foo.tar.bz2 | grep
'^usr/info/*.info'`) ; do
       (shell out:) system("install-info --info-file=$fn
--dir-file=/usr/info/dir")
    (back in C++) done
   (Yeah, I know my "pseudo-code" looks a lot like sh.)

Whichever.

--Chuck