Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <397F50B2.C98D7424@ece.gatech.edu>
Date: Wed, 26 Jul 2000 16:57:22 -0400
From: "Charles S. Wilson" <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: cygwin@sources.redhat.com
Subject: Re: setup + cygcheck
References: <397F4BE0.DCDD9E52@ece.gatech.edu> <20000726164827.A1436@cygnus.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


> >
> >Three things:
> >
> >#1) should cygcheck be updated to show the new setup database in
> >/etc/setup/installed.db, instead of the old database in HKLM?
> 
> Yes.
> 
> >#2) should setup (the new one) remove the old database from HKLM?
> 
> Yes.
> 
> >#3) shouldn't cygcheck show the installed program info regardless of
> >whether you're running as Administrator or not?
> 
> I don't understand this one.  cygcheck currently does this as a
> side effect of its prior use of the registry (which was one of
> the reasons that I used the registry) and it would do this if
> it dumped the installed.db info.  How does administrator access
> enter into this?

You're right, of course. #3 was there if the answers to #1 and #2 were
'no'.

Okay, now comes the *really* hard question.

Since cygcheck is part of cygwin-1.1.3, should the change in #1 be done
before or after the 1.1.3 release?

#2 is okay, that just affects setup.exe which isn't part of
cygwin-1.1.x...

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com