On Mon, 22 Apr 2002 21:36:46 +1000 Robert Collins <[EMAIL PROTECTED]> wrote:
> > From: Cliff Hones [mailto:[EMAIL PROTECTED]] > > Sent: Monday, April 22, 2002 9:14 PM > > > The problem seems to be that setup doesn't set these > > already-present packages to 'keep' or 'skip' by default, and > > there's no way for the user to find out which packages are in > > this state. > > So you are suggesting that in download mode it should not offer to > upgrade any installed packages by default? Or that it should only offer > upgrades for installed packages without cached files? > > I'll happily accept a (reasonable) patch for the second case, but the > first case also seems counter-intuitive to me. I think he'd be happy at this point if it simply wouldn't default to downloading a file that is already present but not yet installed. directory. > > I can't actually see any advantage in re-downloading the > > packages *by default*. > > The point of 'download' mode is to allow downloads. If you choose not to > install what you have downloaded, what should setup assume that means? The download process should probably not even look at the currently installed status of packages when deciding keep/skip/version in the choose screen, just what files it found in the local directory tree. I am working on a class design that could be used in choose.cc when in download mode to make those decisions. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. -- 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/