From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28212 invoked by alias); 16 Feb 2013 18:39:53 -0000 Received: (qmail 28190 invoked by uid 22791); 16 Feb 2013 18:39:51 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mho-03-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 16 Feb 2013 18:39:44 +0000 Received: from pool-173-76-49-193.bstnma.fios.verizon.net ([173.76.49.193] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1U6mfn-00062d-Cl for cygwin-apps@cygwin.com; Sat, 16 Feb 2013 18:39:43 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 9634D8804A7 for ; Sat, 16 Feb 2013 13:39:42 -0500 (EST) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+j0SRz2TwZsPplsTm/ylNO Date: Sat, 16 Feb 2013 18:39:00 -0000 From: Christopher Faylor To: cygwin-apps@cygwin.com Subject: Re: [PATCH 1/4] setup.exe Message-ID: <20130216183942.GA3969@ednor.casa.cgf.cx> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <51153155.3030404@dronecode.org.uk> <87txpm7atu.fsf@Rainer.invalid> <20130210192320.GA6562@ednor.casa.cgf.cx> <87obfo58ta.fsf@Rainer.invalid> <20130213193003.GA5287@ednor.casa.cgf.cx> <8738wz6h5p.fsf@Rainer.invalid> <20130213220849.GA3922@ednor.casa.cgf.cx> <87hale1vuk.fsf@Rainer.invalid> <20130215002235.GA7542@ednor.casa.cgf.cx> <87r4khwe25.fsf@Rainer.invalid> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87r4khwe25.fsf@Rainer.invalid> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2013-02/txt/msg00156.txt.bz2 On Fri, Feb 15, 2013 at 08:51:46PM +0100, Achim Gratz wrote: >Christopher Faylor writes: >> Actually, it needs to detect when a DLL is being installed. AFAIK, >> that's it. > >The first part (detecting when a file of a certain type or in a certain >location gets installed) was never in question. But you also need to >ensure that the package that contains the autorun script is actually >installed at the most recent version. At least that is the behaviour >that autodep+upset does produce and my assumption is that any >integration into setup.exe needs to keep it that way. Are you trying to say that the package containing an autorun script must run its postinstall.sh before anything else? I don't really see the need for a postinstall.sh for any of the current use cases but, ok, yes, that would be a wrinkle for this scenario. However, I'm comfortable with imposing a "autorun packages should not require a postinstall.sh script to operate" rule.[ >>I don't think detecting when a package is being deleted really matters. > >I don't think I talked about deinstallation. In any case it wouldn't >for autodep; at least not if it continues to work like it already does. We're talking about something that *I* suggested. I'm laying out the ground rules. It actually *does* matter that something should be run when a .info file is deleted but it's not a crucial thing to implement right now. >> You can certainly parse regex's in c++ without relying on std::regex. > >Sure, but do you have a suggestion on exactly how? Whatever library >gets chosen it would need to be linked into the executable. It doesn't have to be a library. Cygwin's regexec.c would probably suffice. >> Huh? That would not help with the very case that we're talking about - >> dlls. > >Autodep is used three times (if I counted correctly) in the current >distribution. One is for cygwin, which we don't really need it since it >is already taken care of in a different way in setup.exe. I removed the autorun from cygwin's setup a couple of days ago since it has outlived its usefulness. It actually did do something that wasn't covered by setup.exe but that no longer matters. >The other two are for _autorebase and _update_info. Of these, one >regex matches on files having certain extensions and the other matches >on files installed into directories having certain path prefixes. So >satisfy the current uses of autodep ??? or am I missing something? I actually posted the current autodep line for the _autorebase package. It did not (and should not) rely on file prefixes. cgf