On Fri, 4 Apr 2003, Robert Collins wrote: > Alan Dobkin wrote: > > > > Each time I run it against a local mirror, it checks the MD5 sum > > of every package in the mirror. This is a time-consuming process > > and, unless the window remains in the foreground the entire time, > > it seems to hang. During this time, the status bar is frozen, > > the window doesn't repaint, and it cannot be moved. Eventually, > > once it finishes all of the MD5 checks, it displays the package > > selection screen and then works normally. > > There is a status bar that should be udpating. I'm not sure it > doesn't for you.
I do see the status bar and it does update fine as long as I leave the setup window in the foreground. However, as soon as I click on another window to let it process in the background, that's when the behavior I described occurs. I have tested this on several different computers, including a mixture of Windows 2000 and Windows XP. > > My question is this: Why is it necessary to scan every package > > in the mirror every time setup is run against a local mirror? > > Most of the time, I am only installing a single package or a > > few updates. It seems that setup should only check the packages > > being installed, and the rest of them should be ignored. > > How do you create / maintain that local mirror. Via setup, or via > an external script of some sort? Using wget, as recommended from the Cygwin web site. I've been doing this the same way for at least a year, and it has worked fine for all previous setup releases. Thanks, Alan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
