X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=QlIm7M
	LyIt7xkqVKzMftLQ+7+O00UODbpncI2QmtE7c4yHCSnb6RvxlwS/hbnfYYc4v062
	+kCCOwE4tVhR9J2DXgtJQBdMH0QPbl4bZKUqGqx91gNpFHDoddEVMuHySDubwr4X
	yzRnGJKu48Xf2SVSO6Ujo0V2B6D8LU2rKiVo4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; s=default; bh=L+aZn4m6YqNV
	g1+wacOAlOP9Qc0=; b=PmmOnMzm1sHibugHnBy4vOvEAhVajD6uawk7n/hmzl46
	NhpdMjiMhFOxpD0Vt7esTKaI3M8zlWpsmA5RCYCCFXn0z7/kPLWc4X27X/HOM35k
	f2xf2IT0rNBLArPoTetZef9gott0J0Piwn7Laq/A94AKQOaqg44RHS29o8qRJuY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*M:smtp, Hx-spam-relays-external:sk:smtp-cl, H*RU:sk:smtp-cl, H*r:sk:smtp-cl
X-HELO: lb2-smtp-cloud9.xs4all.net
Date: Tue, 23 Oct 2018 13:47:16 +0200
Message-ID: <d0ae3814736793f9859ecfc68dcd7785@smtp-cloud9.xs4all.net>
From: Houder <houder AT xs4all DOT nl>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: RE: Setup missing installed packages
References: <AM6PR03MB355860F4DD0041D3945CF266BEF40 AT AM6PR03MB3558 DOT eurprd03 DOT prod DOT outlook DOT com> <AM6PR03MB3558F854CA41D3CC94F0417DBEF50 AT AM6PR03MB3558 DOT eurprd03 DOT prod DOT outlook DOT com> <AM6PR03MB35583BC367589E4B9E6567E6BEF50 AT AM6PR03MB3558 DOT eurprd03 DOT prod DOT outlook DOT com>
In-Reply-to: <AM6PR03MB35583BC367589E4B9E6567E6BEF50@AM6PR03MB3558.eurprd03.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=fixed
User-Agent: mua.awk 0.99

On Tuesday, October 23, 2018 10:55 AM Michael Lemke wrote:
[snip]

> Thanks, I did and I can't find anything wrong. Where does setup.exe gets
> the information from? I tried several versions, the current official one,
> the new snapshot and something older I have lying around. They all do
> this. They are in my distribution directory with all the Cygwin downloads
> and all show the correct location of distribution directory
> and installation directory. Some junk in the registry?

uhm ...

Data stored in the registry (Cygwin_root, local_repo):

For a 32-bits instance of Cygwin,
    see HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin

For a 64-bits instance of Cygwin,
    see HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin

.. but if you are using a fixed location for your Cygwin_root and
for your local_repo (distribution directory), why not:

 - create a shortcut to the setup executable ...
 - and add -n -R x:/your_root -l x:/_your_local_repo as arguments
   to the invocation of the executable
   ( x = your drive letter)

and force yourself to use that shortcut?

That would override any default (either by the setup executable or
by you in the past).

.. and save you the trouble of posting to this list.

Regards,
Henri


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple