From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19565 invoked by alias); 16 Jul 2007 10:44:09 -0000 Received: (qmail 19554 invoked by uid 22791); 16 Jul 2007 10:44:08 -0000 X-Spam-Check-By: sourceware.org Received: from pool-71-248-179-128.bstnma.fios.verizon.net (HELO cgf.cx) (71.248.179.128) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 16 Jul 2007 10:44:07 +0000 Received: by cgf.cx (Postfix, from userid 201) id 40CFE2B352; Mon, 16 Jul 2007 06:44:13 -0400 (EDT) Date: Mon, 16 Jul 2007 10:44:00 -0000 From: Christopher Faylor To: cygwin-apps@cygwin.com Subject: Re: cygport: patches welcome? Message-ID: <20070716104413.GB3571@ednor.casa.cgf.cx> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <4696F3CE.9060304@byu.net> <4696F3CE.9060304-PGZyUNKar/Q@public.gmane.org> <20070713080632.GL6851@calimero.vinschen.de> <85je93p679ere7v9m44n5292vb5hro409h@4ax.com> <20070713110653.GO6851@calimero.vinschen.de> <20070716082154.GZ6851@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070716082154.GZ6851@calimero.vinschen.de> User-Agent: Mutt/1.5.15 (2007-04-06) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2007-07/txt/msg00087.txt.bz2 On Mon, Jul 16, 2007 at 10:21:54AM +0200, Corinna Vinschen wrote: >On Jul 13 13:06, Corinna Vinschen wrote: >> On Jul 13 05:58, Andrew Schulman wrote: >> > I think that this won't be necessary if we use Dave's suggestion to remove >> > config files in preremove scripts if they haven't changed. Then all the >> > postinstall script has to do is >> > >> > if [ -f /etc/file ] ; then >> > exit 32 >> > else >> > cp /etc/defaults/etc/file /etc >> > fi >> > >> > (but with smarter exit handling). >> >> Hmm, yes, that doesn't sound bad. >> >> > How about both: postinstall scripts that weren't able to update a config >> > file because it was modified exit with signal 32 (or whatever; I suggest a >> > power of 2 so we can use bitmasks). If any postinstall scripts exit with >> > 32, then setup searches for .cygnew files in /etc and presents the list to >> > the user. A side effect of this would be that each time a config file >> > can't be updated, setup would present the entire list of .cygnew files to >> > the user-- even if they were there from a previous installation, so the >> > user had already been notified about them before. I think this would >> > probably be okay, maybe even good, as long as the user didn't get a new nag >> > screen *every* time they installed any new package-- only when a config >> > file couldn't be updated. >> >> I agree. > >Any comment from our setup gurus? I have no comment other than to note that you can't "exit with signal 32". You can "exit 32" but you can't "kill -32 $$". cgf