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:message-id:date:from:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=K+PhveKkbhKtILS+
	FuqNaD7jk67VyspVwId8jsfPeek3eOgK7ya8yn4Qm1u8bFjcurAkUkjp5BtDLASN
	MBKyYD9dODnur8/eIYqQXAdIZpvtIKabAAFjchR9xGwFJ9R89PnrfeLdJzC6xPyg
	QdQfYwUW3zVeM3o2o8ZTC2RjjLg=
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:message-id:date:from:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=ut25Autk6Y+WiRtYYVG6RK
	9upjw=; b=JwXXFRhFTGkFeChHMm0LoIgks7vkPYqkNj+vxZNihH0bearhE2Arcv
	z0RCK0Vu6tvAFvG1Kkk0Otq6rSPhHUSnoDhSPUQTPfiQaTRahZN4GWMFxXnmnEG5
	hnIOVg+sB/drK+frZ9gNA6wER7Wruy8jbwVuK66T5gPckeJkBKztM=
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=-6.2 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2 autolearn=ham version=3.3.1 spammy=fe, roaming
X-HELO: Ishtar.sc.tlinx.org
Message-ID: <5D5B394B.9050705@tlinx.org>
Date: Mon, 19 Aug 2019 17:05:31 -0700
From: L A Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com, Andrey Repin <anrdaemon AT yandex DOT ru>
CC: David Karr <davidmichaelkarr AT gmail DOT com>
Subject: Re: Win7 update may create confusing Cygwin changes
References: <CAA5t8VocmswTXD4Y7QLxe1NkbZ0Jj+Nt40dFXjHF+9cTP8zW3A AT mail DOT gmail DOT com> <5D571D62 DOT 5040104 AT tlinx DOT org> <15610238789 DOT 20190819141409 AT yandex DOT ru>
In-Reply-To: <15610238789.20190819141409@yandex.ru>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hi Andrey!

On 2019/08/19 04:14, Andrey Repin wrote:
> However, with all due respect, you should follow your own advice first.
> There's more ways to resolve this, and all of them are more correct, than
> generating static files which would get stale rather fast.
---
	How do the static files get stale?  Only time I've seen
has been if I did something to require a new local machine image
(reinstall windows, or move hard disk to new, working machine, etc)
which cause the local machine and rid's to change.  What are you
talking about when you say stale?


> F.e. you could try setting
> db_home: windows
> for it to pick your system profile directory.
---
	But do you know what it does if you have a roaming
profile?

	With a roaming profile, which I _had_ for
over 15 years, it would come up with different values for USERPROFILE
based on *something*, that different from HOME (as a composite
of $HOMEDRIVE$HOMEPATH).  Now I dunnow if one value or the other
was 'stale', but having it change wasn't what I wanted.

	That made software expecting USERPROFILE = HOME or
such, get confused.

	So i'm interested in situations where what I have won't work
(the places where you say it gets 'stale')....  Could you elaborate\
please?





--
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