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
