Dave Korn wrote:
if lots of packages register check-callbacks with cygcheck, we're going to end up (implicitly) making it dependent on a whole lot of other stuff being there and working.
You could create a new directory, say /etc/cygcheck[.d]. Any package that wants cygcheck to run a test for it could put a script in there, which cygcheck would run. Then cygcheck doesn't need to have built-in knowledge of what scripts it should try to run.
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
