Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Mon, 12 Nov 2001 13:01:34 EST To: cygwin-apps AT sources DOT redhat DOT com Subject: Re: Setup snpshot bug no skip/keep 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: <042f01c16b06$67ae3350$0200a8c0@lifelesswks> References: <200111091357 DOT IAA29622 AT cs DOT umb DOT edu> <20011109111617 DOT F24506 AT redhat DOT com> <042f01c16b06$67ae3350$0200a8c0 AT lifelesswks> Robert Collins wrote: > The problem with 4 buckets is that either 1 is a pointer to another or > you have to remember to change 2 whenever you change one. Both of which > will be annoying. When this becomes a bit more oop, this can be made > transparent, and then it will be easier. I'm confused - remove the current Info for installed and add a new bucket for installed in the Info structure that keeps track of Prev, Curr and Test. You still are only updating one installed bucket. > > The current UNKNOWN bucket, IMO should be used to store the installed > package details IFF it's not listed in setup.ini. That works for me - I guess I just don't see why the installed Info Structure is separate from the info Info Structure as we discussed above. But I think in some earlier versions before the heavy rewrites we did use Unknown for an installed version not in setup.ini - at least that was the trust we used although we may not have used that part of the structure. > Also local tarballs should be included, and the bucket count should be > dynamic. Absolutely. bk