[RFC] incremental rebase

[Achim Gratz]

Yaakov Selkowitz writes:
> As things stand now, EVERY package should requires: cygwin, all
> packages with DLLs should requires: _autorebase, and all packages with
> info files should requires: _update-info-dir.  As you can see from
> setup.ini, that's clearly not happening, nor have I managed to find
> any rhyme or reason for those that do versus those that don't.

The real question is why upset is supposed to handle that rather than
setup.exe… I was under the impression that this had been the purpose of
moving the regex library into setup.exe, but I may have misunderstood.

>> I'm opposed to a complete manual assignment of this order on principle.
>> First, it isn't needed for the majority of things
>
> Exactly: a few known tasks -- most of which are already handled by
> cygport -- will need to be planned out, and everything else can go in
> a range where order doesn't really matter.

Dependency order still matters, I suppose.

>> and second, it has the very real potential of requiring huge package rebuild
>
> We need _one_ anyway, but how do you foresee this requiring more later?

Even if we can't think of that need now, it will be present in the least
convenient moment.

>> Unless we've got all packages produced from cygport and a build system that
>> ensures a consistent state of the distribution this is not going to fly.
>
> TBH, that is the goal.

I'm not holding my breath.  BTW, I just got a Windows 8.1 w/ Bing box
that I intend to use as a build machine (it still needs an SSD for the
mirror and build area), so I might try to put something like Hudson on
there as well.

>>> * base-cygwin's postinstall would be 00-cygwin-filesystem.sh, in which
>>> case it could even be part of cygwin itself, since the only need for a
>>> separate base-cygwin is to be first in deptree;
>>
>> Put it on an appropriate stratum.
>
> Huh?

Did you read my proposal?

> While I generally agree wrt clobbering, postinstall scripts are (the?)
> one place where it is not a problem because the scripts are renamed to
> .done after being executed.  As for the contents of the scripts, they
> would all be identical because they would all be generated by cygport.

Yes, and if you have to change that script, suddenly all packages have
to be rebuilt and the [prev] packages don't work anymore.  No, thanks.
Plus, at least for now not all maintainers use cygport, so that would
put another requirement on them to keep things straight manually.


I've had the impression that Corinna wanted to get something _now_ (and
Ken too, most likely).  That implies we can't change certain things (the
format and semantics of setup.ini or setup.hint for instance) and that
puts shifts most of the functionality into setup.exe (where a lot of it
belongs to, anyway).  You seem to propose something that has no
immediate consequences and produces at least one big-bang event some
time in the future.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables