This is the mail archive of the cygwin-apps mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Nov 21 23:13, Achim Gratz wrote: > Corinna Vinschen writes: > > I don't understand this one. The lst.gz files don't tell you which > > of them are newly installed/updated. But, anyway, I trust that you > > had that thought out. > > They have a newer time stamp than the last list that has been extracted. > Again, pattern matching inside setup.exe would cover a few corner cases, > but checking timestamps is reliable enough otherwise. > > > Ideally I'd prefer if setup would only do the generic part of this, > > collecting and propagating information of new or updated files, running > > scripts using a pattern-based algorithm, whatever. It shouldn't run > > specific scripts based on hardcoded rules. > > That then requires directives in setup.ini ==> longer term. > > > Simple triggers based on file suffixes might be nice: > > > > 1t-dll,so,oct-rebase.bat > > 2t-info-update-info-dir.bat > > > > I'm surr you can guess how and when I mean them to run ;) > > Yes, only that I wouldn't want to try to extract these things from the > script name. The logical place for such rules would be setup.ini, since > then these can be changed while generating this file with or without > cooperation from the packager. But then you're requiring the "autodep" logic in upset again, which is what we want to get rid of in the first place since it doesn't seem to work reliably. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Attachment:
pgpsxjPC7pzqk.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |