On 22/09/2015 18:32, Achim Gratz wrote:
Jon Turney writes:
Since we now have scripts which run on every setup run, a package which requires
another package to do some work after it is installed or uninstalled can create
a file to act as a trigger for that to happen.
There aren't any stratified scripts for pre-remove, so a lot of the
things that you might wish for don't work anyway. So again it would
need to be fixed without getting a trigger or setup would need to be
made a lot smarter than it is today.
I thought that permanent postinstall scripts run even when no packages
are being installed, or only packages are being removed, so they they
are effectively run every time setup is?
Unfortunately, it's not very practical to change to doing that for the all
packages which contain info files, so I am suggesting this approach.
So just do it unconditionally; I was planning to change _update-info-dir
accordingly, but haven't found the time yet. I do the same with mandb
locally already and I haven't looked back.
Tempting, but I don't believe that is a good solution, since it adds the
time it takes to rebuild the info directory to every setup run.
$ time /etc/postinstall/update-info-dir.sh.done
real 0m18.169s
user 0m3.261s
sys 0m5.703s
I also don't think it sets a good example. Any other packages which
require update scripts to run (which may take even longer) when packages
are installed/removed, should not be doing that every time setup is run,
if avoidable.
--
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
