Re: Setup request
Buchbinder, Barry (NIH/NIAID) [E] writes: > Even when nothing is updated, setup seems to rebase and run all the > /etc/postinstall/zp_* files. This is exactly as intended. > This seems unnecessary. It isn't. There is no way to know if there have been any changes made either by a previous run of setup that didn't complete or from outside setup that needs attention. These scripts are intended to expend the least possible effort to check if there is something to do and exit at the earliest moment. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Setup request
To keep up to date, every day when booting I automatically update Cygwin with the following in a startup batch file. setup -B -q -n -o -R -l Even when nothing is updated, setup seems to rebase and run all the /etc/postinstall/zp_* files. This seems unnecessary. If that is correct, would it be possible to have setup always skip rebase & zp_* when not packages are updated, or at least have a command line option to skip rebase and running zp_*? I'm not a developer, so I cannot contribute a patch. Sorry. Thanks for considering this. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
