Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Michael Ring <m DOT ring AT ndh DOT net>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Added crude update ability to setup.exe
Date: Sun, 30 Apr 2000 10:51:22 +0200
Message-ID: <9e4LOa1ZbSJTTh6WjhyJ43fF+F2S@4ax.com>
References: <38E23135 DOT BB92EF81 AT fc DOT hp DOT com> <slrn8e4cf8 DOT 5e1 DOT hildeb AT stahlw06 DOT stahl DOT bau DOT tu-bs DOT de> <38E23D5D DOT 72E7F9C6 AT fc DOT hp DOT com> <kuu2hnihlq DOT fsf AT lasipalatsi DOT fi>
In-Reply-To: <kuu2hnihlq.fsf@lasipalatsi.fi>
X-Mailer: Forte Agent 1.6/32.525
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id DAA03040

>I just made some changes to setup:
>
>1) Store version information, gleaned from filenames in the registry.

>2) Accept a "-u" option which will cause setup to run in "update mode", only
>  downloading or installing newer versions of .tar.gz files.

>3) Accept a list of packages to install on the command line.

>If setup.exe detects that an attempt is being made to install to a
>directory which seems to already have cygwin 1.1.0 in it, but there is
>no version information in the registry, it will ask the user if it
>should update the registry with default settings, appropriate for the
>previous installation.
>
>Anyway, what I'm aiming for is to be able to do something like this:
>
>setup -u cygwin
>
>And, for the most part, this works fine.  One problem I have is that,
>right now, setup.exe uses HKLM to store the list of packages that >have
>been installed.  I guess I'll have to also use HKCU if the user can't
>write to HKLM.

Nope, you should not go for HKCU; this is for user-information, not
for machine-specific application information.

The first real problem shows up if the user has a roaming profile,
which means his profile is placed on a central site in the network.
The profile follows the user to every machine he is logged on. So
setup would see version information that does not match the version
installed on the machine.

Normaly there is no write-protection in HKLM/SOFTWARE so there should
be no problem.

If it were, the / - mount for cygwin could not work because it is
stored in HKLM/SOFTWARE.

Greetings,

Michael Ring