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: <3BF4976E.5070606@ece.gatech.edu>
Date: Thu, 15 Nov 2001 23:34:54 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
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> <20011116032354 DOT GA14158 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:


>>*Well* beyond the newbie's capability.  But "reinstall the info package" or 
>>"run fix-info" is nice and simple.
>>
> 
> Sure.  If you've got a solution, I have no objections.  I just didn't
> think it was a big deal, either way.
> 
> And, ur, I've been one of those screwed up package maintainers.  I don't
> even currently rebuild dir in any of my packages and I really should.
> 
> Or, actually, I think either setup.exe should be intelligent enough to
> do this for you or there should be some way for a package to say "please
> run this standard bit of machinery for me".


You mean setup.exe itself should do:
   if tarball contains /usr/info/*, then
     install-info --dir-file=/usr/info/dir --info-file=$(each one)
   end

I disagree.  AFAIK, RPM doesn't do this.  I believe you have to do:

%post
install-info .....

in the spec file.  Which is analogous to each of *our* packages that have 
info files providing an /etc/postinstall/pkg.sh script to handle the 
operation for its own info files.

It's a bit painful to munge a package's Makefiles to install a "random" 
file like "autoconf.postinstall" into "/etc/postinstall/" -- but both my 
proposal and Robert's proposal use an *external* script/makefile to drive 
package building -- and in THAT script/makefile, installing the postinstall 
file is a cinch.

Point: energy barrier for maintainers to do this sort of thing will be 
lower after the new -src standard is specified.  Especially if folks just 
copy/adapt the build scripts that Robert and I have been throwing around.

--Chuck