On Nov 11 18:37, Ken Brown wrote: > On 11/11/2014 12:08 PM, Achim Gratz wrote: > >As Ken already correctly summarized, the autorebase postinstall script > >will never be marked as done by setup.exe, so it will be run on each > >install or update. The incremental part ensures that this step doesn't > >take too much time if there's nothing to do. Currently this is based on > >the name of that script, but it could be done differently. The other > >part is that all "perpetual" postinstall scripts are run before any > >normal postinstall scripts, so these can assume to run in a correctly > >rebased environment. > >[...] > >A slightly modified variant of the same mechanism could be used for > >those infodir, icon cache and fontconfig updates, which should probably > >be run after the normal postinstall scripts. I think I've sent Ken a > >sketch doing this from within a postinstall script for the texlive > >packages, but providing some support from setup.ini and setup.exe for > >stratified postinstalls (pre-post and post-post :-) would make this much > >more robust. I haven't yet coded up anything in that direction, though. > > > >If you're wondering what happens when you've just installed a fresh > >Cygwin: the perpetual rebase postinstall scripts detects the situation > >and bails out, while the normal postinstall script does the initial > >rebase (and is marked "done"). Which means we have to fix the > >dependency problem anyway. > > > >Incremental autorebase packages and patched setup.exe available on > >request. > > I'd like to see them. Thanks.
Yes, me too. Achim, does your perpetual autorebase rely on the existing autorebase script? If so, do you see a good chance to consolidate the changes into a single package we're still calling _autorebase? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpSjl3tKSBc6.pgp
Description: PGP signature
