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:mime-version:content-type :content-transfer-encoding:date:from:to:subject:message-id; q= dns; s=default; b=Q2OOsU6T1Zlmecti0kjr7FexwprZPL0UFnYdYgk2IV8tu0 dXA8/ooZ5Wh2Z+lvA+RL8Az6ZWI1hK4lCl0rpU1XGal5WL1v9RX+iX4eVu70uOix K7Az/vlnba1HuGq1dEThkRVb1yBbk9xhoz8F9lVK+BaBmyGmuK0YG5nYHUCQo= 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:mime-version:content-type :content-transfer-encoding:date:from:to:subject:message-id; s= default; bh=PzMoiIGNw8KQqik1rp3EbzJ3xY8=; b=lZ05Y2+oTQUMiLJAsaI9 A3uPKUCSk3rCx7wt8HRamyNA69R+rMGvwhXcmVx/9C2wOyiUjAecgj/IJ0K86B88 mS45RVgRbTdZMhU6IDyHFRpIYvOEuQ5IJNetokrq9h1a+LqcmDjbLEyF6ecP+OxG 2xeRIRsBXw4A4bxgeSUKtmo= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.4 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=consult, ic, cygwin64, H*r:109 X-HELO: lb2-smtp-cloud7.xs4all.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 04 Apr 2019 12:09:28 +0200 From: Houder To: cygwin AT cygwin DOT com Subject: setup: why consult registry (rootdir) if -R has been specified? Message-ID: X-Sender: houder AT xs4all DOT nl User-Agent: XS4ALL Webmail X-IsSubscribed: yes Hi Jon, My question is about setup.exe. Why does setup _initially_ consult rootdir in registry if -R has been specified ? (and yes, there is an installation at the rootdir that I specify w/ the -R option) This is my workflow: - I use a shortcut to invoke setup.exe - my shortcut specifies -R and -l (i.c. root directory and local directory) e.g. E:\_cygwin64_repository\setup-2.897-x86_64.exe -n -R e:/Cygwin64 \ -l e:/_cygwin64_repository (start directory: E:\_cygwin64_repository) - updating occurs in two steps: 1. download (w/o installing) to local directory 2. install fr. local directory - I am using multiple 64-bits installations (installing packages from a specific local directory, dependent on the _chosen_ root directory) i.e. e:/_cygwin64_repository => e:/Cygwin64 e:/_cygwin64-test_repository => e:/Cygwin64-test etc. I understand the need for - /etc/setup/installed.db ("what is installed"), and - /etc/setup/setup.rc - last cache (aka local directory or repository) - last mirror - last action /HKLM/Software/Cygwin/setup in registry shows the root directory: Either key = rootdir, value = e:\Cygwin64 or key = rootdir, value = e:\Cygwin64-test The value in registry changes if I "install fr. local directory" and if I complete this step (next, next (ok), finish). In all other cases, the value remains UNchanged. /etc/setup/setup.rc in the root directory is updated after each invocation of setup; that is, the root directory corresponding to the directory specified w/ the -R option. Splendid. However when I invoke setup (using the shortcut), setup appears to consult /etc/setup/setup.rc in the root directory as specified by the registry, NOT as specified by the -R option. As result, setup (nearly) always shows _ME_ the WRONG last action when it is started (as I switch a _lot_ between the installations that I have). Why does setup _initially_ ignore the root directory as specified by the -R option, showing (me) the wrong last action (in my case)? 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