Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 02 Jul 2001 12:54:11 EDT To: cygwin-developers AT cygwin DOT com Subject: Re: Local Setup Cache X-Mailer: Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va Message-Id: From: Brian Keener Reply-To: bkeener AT thesoftwaresource DOT com In-Reply-To: <20010630164414.A16520@redhat.com> References: <00b701c1010a$39ddea30$6464648a AT ca DOT boeing DOT com> <20010629223139 DOT B11334 AT redhat DOT com> <008a01c1013a$470a8fd0$6464648a AT ca DOT boeing DOT com> <20010630120156 DOT C12695 AT redhat DOT com> <00a001c1017f$42fdd3d0$6464648a AT ca DOT boeing DOT com> <20010630153950 DOT C16134 AT redhat DOT co <20010630164414 DOT A16520 AT redhat DOT com> Christopher Faylor wrote: > >2. A check box in "Local Package Directory" dialog box labeled "Delete > >Obsolete Package Files". If it defaults to checked, the Vanilla Users will > >never have to worry about it. > FWIW, I like this one as well but with a catch - even if the package is not listed in setup.ini (ie it is obsolete) but if it is still considered the installed version it stays. Not until it has been replaced by another install and exists no longer in setup.ini is it considered obsolete. bk