[RFC] incremental rebase

Achim Gratz Stromeko@nexgo.de
Fri Nov 21 22:13:00 GMT 2014

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.  There'd certainly be a handful of
"global" rules not associated with any specific package while some
packages might want to use it for package specific purposes.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:

More information about the Cygwin-apps mailing list